Memory system

ABSTRACT

A memory system may include: a nonvolatile memory device; a volatile memory suitable for storing write data; and a controller suitable for: allocating a normal write buffer in the volatile memory when normal write data are inputted, allocating a first write buffer in the volatile memory when first write data, which are grouped into a first transaction and first total size information on a total size of the first transaction, are inputted, allocating a second write buffer in the volatile memory when second write data, which are grouped into a second transaction and second total size information on a total size of the second transaction, are inputted, managing sizes of the first and second write buffers to change them in response to the first and second total size information, respectively, and managing a size of the normal write buffer to fix it to a set size.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority under 35 U.S.C. § 119(a) to KoreanPatent Application No. 10-2018-0100118, filed on Aug. 27, 2018, which isincorporated herein by reference in its entirety.

BACKGROUND 1. Field

Various embodiments relate to a memory system and, more particularly, toa memory system which stores a plurality of write data grouped into atransaction.

2. Discussion of the Related Art

The computer environment paradigm has changed to ubiquitous computingsystems that can be used anytime and anywhere. Due to this, use ofportable electronic devices such as mobile phones, digital cameras, andnotebook computers has rapidly increased. These portable electronicdevices generally use a memory system having one or more memory devicesfor storing data. A memory system may be used as a main or an auxiliarystorage device of a portable electronic device.

Memory systems provide excellent stability, durability, high informationaccess speed, and low power consumption because they have no movingparts. Examples of memory systems having such advantages includeuniversal serial bus (USB) memory devices, memory cards having variousinterfaces, and solid state drives (SSD).

SUMMARY

Various embodiments are directed to a memory system capable ofeffectively managing a plurality of write data grouped into atransaction.

In an embodiment, a memory system may include: a nonvolatile memorydevice; a volatile memory suitable for temporarily storing write datainputted from a host; and a controller suitable for: allocating a normalwrite buffer in the volatile memory when normal write data, which arenot grouped into a transaction, are inputted from the host, allocating afirst write buffer in the volatile memory when first write data, whichare grouped into a first transaction and first total size information ona total size of the first transaction, are inputted, allocating a secondwrite buffer in the volatile memory when second write data, which aregrouped into a second transaction and second total size information on atotal size of the second transaction, are inputted, managing sizes ofthe first and second write buffers to change them in response to thefirst and second total size information, respectively, and managing asize of the normal write buffer to fix it to a set size.

the controller may further: check a first determined size for the firstwrite data according to the first total size information, and allocatesthe first write buffer by an amount of the first determined size in thevolatile memory, and check a second determined size for the second writedata according to the second total size information, and allocates thesecond write buffer by an amount of the second determined size in thevolatile memory.

The controller may further: check whether the first transaction iscommitted or aborted, for the first write data stored in the first writebuffer; perform a first write operation of storing the first write datastored in the first write buffer in the nonvolatile memory device byperforming a first flush operation for the first write buffer, in thecase where the first transaction is checked as being committed, and thenreleases the first write buffer in the volatile memory, and release thefirst write buffer in the volatile memory in the case where the firsttransaction is checked as being aborted.

The controller may further: check whether the second transaction iscommitted or aborted, for the second write data stored in the secondwrite buffer, perform a second write operation of storing the secondwrite data stored in the second write buffer in the nonvolatile memorydevice by performing a second flush operation for the second writebuffer, in the case where the second transaction is checked as beingcommitted, and then releases the second write buffer in the volatilememory, and release the second write buffer in the volatile memory inthe case where the second transaction is checked as being aborted.

The controller may further: synchronize a start time of the first flushoperation and a start time of the second flush operation in the casewhere a time at which commit of the first transaction is checked and atime at which commit of the second transaction is checked are within aset first time interval.

When the start time of the first flush operation and the start time ofthe second flush operation are synchronized, the controller maysynchronize a time at which a first acknowledgement signal correspondingto completion of the first write operation is transferred to the hostand a time at which a second acknowledgement signal corresponding tocompletion of the second write operation is transferred to the host.

When a time at which a first acknowledgement signal is generated and atime at which a second acknowledgement signal is generated are within aset second time interval, the controller may synchronize a time at whichthe first acknowledgement signal is transferred to the host and a timeat which the second acknowledgement signal is transferred to the host.

The controller may receive a plurality of write commands respectivelycorresponding to the write data, from the host, transaction informationof the respective write data corresponding to the write commands may berespectively included in the write commands, transaction information ofeach of the write data may include transaction ID (identification)information, commit information and abort information, the first totalsize information may be additionally included in a write commandcorresponding to start data of the first transaction among the firstwrite data, and the second total size information may be additionallyincluded in a write command corresponding to start data of the secondtransaction among the second write data.

The controller may further: check transaction ID information in thetransaction information of the respective write data, store the firstwrite data by allocating the first write buffer in the volatile memoryin the case where the transaction ID information of the first write datawhich are grouped into the first transaction are checked as being set toa first value, store the second write data by allocating the secondwrite buffer in the volatile memory in the case where the transaction IDinformation of the second write data which are grouped into the secondtransaction are checked as being set to a second value, and store thenormal write data by allocating the normal write buffer in the volatilememory in the case where the transaction ID information of the normalwrite data are checked as not being set and thus which are not groupedinto a transaction.

In an embodiment, a memory system may include: a nonvolatile memorydevice; a volatile memory suitable for temporarily storing write datainputted from a host; and a controller suitable for: allocating aplurality of write buffers, each of which has a defined size, in thevolatile memory, storing normal write data, which are inputted from thehost and are not grouped into a transaction, in write buffers which arenot set for exclusive use for transactions, and setting, when firstwrite data which are grouped into a first transaction and first totalsize information on a total size of the first transaction are inputtedfrom the host, a first exclusive use option for exclusively using atleast one first write buffer among the write buffers, for the firsttransaction, according to the first total size information.

The controller may further: check respective empty spaces of the writebuffers at a time when the first write data are inputted from the host,set the first exclusive use option for a minimum number of write buffersamong the write buffers, according to the checked empty spaces and thefirst total size information, and use the minimum number of writebuffers as the at least one first write buffer.

The controller may further: set, when second write data which aregrouped into a second transaction and second total size information on atotal size of the second transaction are inputted from the host, asecond exclusive use option for exclusively using at least one secondwrite buffer among remaining write buffers excluding the first writebuffer, for the second transaction, according to the second total sizeinformation,

The controller may further: check respective empty spaces of theremaining write buffers at a time when the second write data areinputted from the host, set the second exclusive use option for aminimum number of write buffers among the remaining write buffers,according to the checked empty spaces and the second total sizeinformation, and use the minimum number of write buffers as the at leastone second write buffer.

The controller may further: check whether the first transaction iscommitted or aborted, for the first write data stored in the at leastone first write buffer, perform a first write operation of storing thefirst write data stored in the at least one first write buffer in thenonvolatile memory device by performing a first flush operation for theat least one first write buffer, in the case where the first transactionis checked as being committed, and then resets the first exclusive useoption for the at least one first write buffer, and discard the firstwrite data stored in the at least one first write buffer in the casewhere the first transaction is checked as being aborted, and then resetsthe first exclusive use option for the at least one first write buffer.

The controller may further: check whether the second transaction iscommitted or aborted, for the second write data stored in the at leastone second write buffer, perform a second write operation of storing thesecond write data stored in the at least one second write buffer in thenonvolatile memory device by performing a second flush operation for theat least one second write buffer, in the case where the secondtransaction is checked as being committed, and then resets the secondexclusive use option for the at least one second write buffer, anddiscard the second write data stored in the at least one second writebuffer in the case where the second transaction is checked as beingaborted, and then resets the second exclusive use option for the atleast one second write buffer.

The controller may further: synchronize a start time of the first flushoperation and a start time of the second flush operation in the casewhere a time at which commit of the first transaction is checked and atime at which commit of the second transaction is checked are within aset first time interval.

When the start time of the first flush operation and the start time ofthe second flush operation are synchronized, the controller maysynchronize a time at which a first acknowledgement signal correspondingto completion of the first write operation is transferred to the hostand a time at which a second acknowledgement signal corresponding tocompletion of the second write operation is transferred to the host.

When a time at which a first acknowledgement signal corresponding tocompletion of the first write operation is generated and a time at whicha second acknowledgement signal corresponding to completion of thesecond write operation is generated are within a set second timeinterval, the controller may synchronize a time at which the firstacknowledgement signal is transferred to the host and a time at whichthe second acknowledgement signal is transferred to the host.

The controller may receive from the host a plurality of write commandsrespectively corresponding to the write data, transaction information ofthe respective write data corresponding to the write commands may berespectively included in the write commands, transaction information ofeach of the write data may include transaction ID (identification)information, commit information and abort information, the first totalsize information may be additionally included in a write commandcorresponding to start data of the first transaction among the firstwrite data, and the second total size information may be additionallyincluded in a write command corresponding to start data of the secondtransaction among the second write data.

The controller may further: check transaction ID information in thetransaction information of the respective write data, store the firstwrite data by setting the first write buffer among the write buffers inthe case where the transaction ID information of the first write datawhich are grouped into the first transaction are checked as being set toa first value, store the second write data by setting the at least onesecond write buffer among the remaining write buffers in the case wherethe transaction ID information of the second write data which aregrouped into the second transaction are checked as being set to a secondvalue, and store the normal write data in remaining write buffers exceptthe first and second write buffers among the write buffers, in the casewhere the transaction ID information of the normal write data arechecked as not being set and thus which are not grouped into atransaction.

In an embodiment, a memory system may include: a nonvolatile memorydevice suitable for storing write data; a volatile memory devicesuitable for buffering the write data; and a controller suitable forcontrolling the nonvolatile memory device to store the write data byflushing the buffered write data into the nonvolatile memory device. Thecontroller may assign, within the volatile memory device, a first bufferspace of a variable size according to a total size of the write datawhen the write data is identified as transaction data. The controllermay assign, within the volatile memory device, a second buffer space ofa fixed size when the write data is identified as normal data, which isdifferent than the transaction data.

In the present technology, when write data which are grouped into atransaction are inputted from a host, a dedicated transaction writebuffer is allocated in a volatile memory. The transaction write buffermay be distinguished from a normal write buffer for managing normalwrite data. Through this, it is possible to effectively managetransaction write data.

Also, upon the completion of at least two transactions, flush operationsof the transaction write buffers may be performed in synchronizationwith each other to the maximum within a possible range. Through this, analgorithm for ensuring transaction data is simplified.

Moreover, upon flush of the transaction write buffers, acknowledgementsignals transmitted to the host are synchronized to the maximum extentwithin a possible range. Through this, the number of times theacknowledgement signals are transmitted to the host is minimized in amemory system.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1 and 2 are diagrams to assist in the explanation of theconfiguration of a data processing system including a memory system inaccordance with an embodiment of the present disclosure.

FIGS. 3A to 3D and 4A to 4D are diagrams to assist in the explanation ofthe operation of the memory system in accordance with an embodiment ofthe present disclosure.

FIGS. 5A to 5C are flow charts to assist in the explanation of theoperation of the memory system in accordance with an embodiment of thepresent disclosure.

FIGS. 6 and 7 are diagrams to assist in the explanation of theconfiguration of a data processing system including a memory system inaccordance with another embodiment of the present disclosure.

FIGS. 8A to 8E and 9A to 9D are diagrams to assist in the explanation ofthe operation of the memory system in accordance with an embodiment ofthe present disclosure.

FIGS. 10A to 10C are flow charts to assist in the explanation of theoperation of the memory system in accordance with an embodiment of thepresent disclosure.

DETAILED DESCRIPTION

Various embodiments will be described below in more detail withreference to the accompanying drawings. The present invention may,however, be embodied in different forms and should not be construed aslimited to the embodiments set forth herein. Rather, these embodimentsare provided so that this disclosure is thorough and complete and fullyconveys the scope of the present invention to those skilled in the art.Throughout the disclosure, like reference numerals refer to like partsthroughout the various figures and embodiments of the present invention.Also, throughout the specification, reference to “an embodiment,”“another embodiment,” “first embodiment,” “a second embodiment” or thelike is not necessarily to only one embodiment, and different referencesto any such phrase are not necessarily to the same embodiment(s).

First Embodiment

FIGS. 1 and 2 are diagrams to assist in the explanation of theconfiguration of a data processing system including a memory system inaccordance with a first embodiment of the present disclosure.

Referring to FIG. 1, the data processing system includes a host A10 anda memory system A20. The memory system A20 includes a controller A30, afirst nonvolatile memory device A40, a second nonvolatile memory deviceA50 and a third nonvolatile memory device A60.

For reference, in FIGS. 1 and 2, three nonvolatile memory devices A40,A50 and A60 are included in the memory system A20. However, this ismerely an example; more or less than three nonvolatile memory devicesmay be included in a memory system. This arrangement is used in thefollowing description, but as indicated above, the present invention isnot limited to such arrangement.

The host A10 transmits a plurality of commands corresponding to a userrequest to the memory system A20, and accordingly, the memory system A20performs operations corresponding to the commands, that is, operationscorresponding to the user request. The data processing system maycomprise one or more memory systems A20, although embodiments of thepresent invention are described in the context of a single memory systemA20.

The memory system A20 operates in response to a request of the host A10,in particular, store data to be accessed by the host A10. In otherwords, the memory system A20 may be used as a main memory device or anauxiliary memory device of the host A10. The memory system A20 may berealized by any one of various kinds of storage devices, depending on ahost interface protocol which is coupled with the host A10. For example,the memory system A20 may be realized by any of a solid state drive(SSD), a multimedia card in the form of an MMC, an eMMC (embedded MMC),an RS-MMC (reduced size MMC) and a micro-MMC, a secure digital card inthe form of an SD, a mini-SD and a micro-SD, a universal serial bus(USB) storage device, a universal flash storage (UFS) device, a compactflash (CF) card, a smart media card, a memory stick, and the like.

The memory system A20 may be integrated into one semiconductor deviceand configure a memory card. For instance, the memory system A20 mayconfigure a memory card such as a Personal Computer Memory CardInternational Association (PCMCIA) card, a compact flash (CF) card, asmart media card in the form of an SM and an SMC, a memory stick, amultimedia card in the form of an MMC, an RS-MMC and a micro-MMC, asecure digital card in the form of an SD, a mini-SD, a micro-SD and anSDHC, and/or a universal flash storage (UFS) device.

For another example, the memory system A20 may configure a computer, anultra mobile PC (UMPC), a workstation, a net-book, a personal digitalassistant (PDA), a portable computer, a web tablet, a tablet computer, awireless phone, a mobile phone, a smart phone, an e-book, a portablemultimedia player (PMP), a portable game player, a navigation device, ablack box, a digital camera, a digital multimedia broadcasting (DMB)player, a 3-dimensional television, a smart television, a digital audiorecorder, a digital audio player, a digital picture recorder, a digitalpicture player, a digital video recorder, a digital video player, astorage configuring a data center, a device capable of transmitting andreceiving information under a wireless environment, one of variouselectronic devices configuring a home network, one of various electronicdevices configuring a computer network, one of various electronicdevices configuring a telematics network, an RFID (radio frequencyidentification) device, or one of various component elements configuringa computing system.

The memory system A20 may include a storage device such as a volatilememory device such as a dynamic random access memory (DRAM) and a staticrandom access memory (SRAM) or a nonvolatile memory device such as aread only memory (ROM), a mask ROM (MROM), a programmable ROM (PROM), anerasable programmable ROM (EPROM), an electrically erasable andprogrammable ROM (EEPROM), an ferroelectric random access memory (FRAM),a phase change RAM (PRAM), a magnetic RAM (MRAM), a resistive RAM (RRAM)and/or a flash memory.

The memory system A20 includes a volatile memory 144 for temporarilystoring write data WDATA inputted from the host A10.

The controller A30 allocates a normal write buffer A31 in the volatilememory 144 in response to that normal write data NMAL_WDATA which arenot grouped into a transaction are inputted from the host A10.

The controller A30 allocates a first write buffer A32 in the volatilememory 144 when first write data TRAN_WDATA1 which are grouped into afirst transaction and first total size information TTSIZE1 on a totalsize of the first transaction are inputted from the host A10.

The controller A30 allocates a second write buffer A33 in the volatilememory 144 when second write data TRAN_WDATA2 which are grouped into asecond transaction and second total size information TTSIZE2 on a totalsize of the second transaction are inputted from the host A10.

The fact that write data WDATA are grouped into a transaction means thata plurality of write data WDATA used for the same purpose among writedata WDATA are grouped into one transaction.

For example, in a database, data used for correction, addition andupdate of already stored data may be grouped into respectivetransactions according to their respective uses. In this regard, datafor correcting a database may be grouped into one transaction group, anddata for adding a database may be grouped into another transactiongroup.

Therefore, when write data TRAN_WDATA1 or TRAN_WDATA2 which are groupedinto one transaction are transmitted from the host A10 to the controllerA30, there exists only a commit state in which all the write dataTRAN_WDATA1 or TRAN_WDATA2 are normally transmitted and stored and arethus valid or an abort state in which any one or both of the write dataTRAN_WDATA1 or TRAN_WDATA2 is not normally transmitted and stored or allthe write data TRAN_WDATA1 or TRAN_WDATA2 are invalid according to anabort request of the host A10. That is, write data TRAN_WDATA1 orTRAN_WDATA2 which are grouped into one transaction are meaningful onlywhen they are in a commit state as all such data are normallytransmitted and stored and are thus all valid.

For example, in order for the first write data TRAN_WDATA1, grouped intoa transaction among the write data WDATA transmitted from the host A10to the controller A30, to be checked as a commit state in the controllerA30, all of the plurality of first write data TRAN_WDATA1 should benormally transmitted from the host A10 to the controller A30 and becompletely stored in the controller A30, and at the same time, thereshould be no abort request from the host A10. If even any one of theplurality of first write data TRAN_WDATA1 is not normally transmittedand stored or an abort request is received from the host A10, all of thefirst write data TRAN_WDATA1 are checked as an abort state in thecontroller A30.

Similarly, in order for the second write data TRAN_WDATA2, grouped intothe second transaction among the write data WDATA transmitted from thehost A10 to the memory system A20, to be checked as a commit state inthe memory system A20, all of the plurality of second write dataTRAN_WDATA2 should be normally transmitted from the host A10 to thememory system A20 and be completely stored in the memory system A20, andat the same time, there should be no abort request from the host A10. Ifeven any one of the plurality of second write data TRAN_WDATA2 is notnormally transmitted and stored or an abort request is issued from thehost A10, all of the second write data TRAN_WDATA2 are checked as anabort state in the memory system A20.

For reference, the operation of managing the write data TRAN_WDATA1 orTRAN_WDATA2 grouped into a transaction, by classifying them into acommit state or an abort state as described above, may be generallyreferred to as an operation for ensuring the transaction.

The reason why the normal write buffer A31 allocated in the volatilememory 144 of the controller A30 is shown by not a solid line but thedotted line in FIG. 1 is because the controller A30 allocates the normalwrite buffer A31 when the normal write data NMAL_WDATA are inputted fromthe host A10. That is, in the case where the normal write dataNMAL_WDATA are not inputted from the host A10, the controller A30 maynot allocate the normal write buffer A31 in the volatile memory 144.

Similarly, the reason why the first write buffer A32 allocated in thevolatile memory 144 of the controller A30 is shown not by a solid linebut by a dotted line in FIG. 1 is because the controller A30 allocatesthe first write buffer A32 when the first write data TRAN_WDATA1 groupedinto the first transaction are inputted from the host A10. That is, inthe case where the first write data TRAN_WDATA1 grouped into the firsttransaction are not inputted from the host A10, the controller A30 maynot allocate the first write buffer A32 in the volatile memory 144.

Similarly, the reason why the second write buffer A33 allocated in thevolatile memory 144 of the controller A30 is shown not by a solid linebut by a dotted line in FIG. 1 is because the controller A30 allocatesthe second write buffer A33 when the second write data TRAN_WDATA2grouped into the second transaction are inputted from the host A10. Thatis, in the case where the second write data TRAN_WDATA2 grouped into thesecond transaction are not inputted from the host A10, the controllerA30 may not allocate the second write buffer A33 in the volatile memory144.

The controller A30 allocates the normal write buffer A31 which is fixedto a set or preset size, in the volatile memory 144, and then, storesthe normal write data NMAL_WDATA inputted from the host A10, in thenormal write buffer A31.

The size of the first write buffer A32 is variable according to thefirst total size information TTSIZE1.

In other words, in response to the first write data TRAN_WDATA1 groupedinto the first transaction and the first total size information TTSIZE1inputted from the host A10, the controller A30 checks a first determinedsize for the first write data TRAN_WDATA1 and allocates the first writebuffer A32 by an amount of the first determined size in the volatilememory 144.

Therefore, the size of the first write buffer A32 may depend on thefirst total size information TTSIZE1.

For example, if the first determined size is checked as ‘5’ in responseto the first total size information TTSIZE1 at a first time, thecontroller A30 allocates a memory region capable of storing five piecesof the first write data TRAN_WDATA1 at the first time, in the volatilememory 144, and manages the memory region as the first write buffer A32.

For another example, if the first determined size is checked as ‘3’ inresponse to the first total size information TTSIZE1 at a second timeother than the first time, the controller A30 allocates a memory regioncapable of storing three pieces of the first write data TRAN_WDATA1 atthe second time, in the volatile memory 144, and manages the memoryregion as the first write buffer A32.

Further, the size of the second write buffer A33 is variable accordingto the second total size information TTSIZE2.

In other words, in response to the second write data TRAN_WDATA2 groupedinto the second transaction and the second total size informationTTSIZE2 inputted from the host A10, the controller A30 checks a seconddetermined size for the second write data TRAN_WDATA2 and allocates thesecond write buffer A33 by an amount of the second determined size inthe volatile memory 144.

Therefore, the size of the second write buffer A33 may depend on thesecond total size information TTSIZE2.

For example, if the second determined size is checked as ‘6’ in responseto the second total size information TTSIZE2 at a third time, thecontroller A30 allocates a memory region capable of storing six piecesof the second write data TRAN_WDATA2 at the third time, in the volatilememory 144, and manages the memory region as the second write bufferA33.

For another example, if the second determined size is checked as ‘4’ inresponse to the second total size information TTSIZE2 at a fourth timeother than the third time, the controller A30 allocates a memory regioncapable of storing four pieces of the second write data TRAN_WDATA2 atthe fourth time, in the volatile memory 144, and manages the memoryregion as the second write buffer A33.

Referring to FIG. 2, the detailed configuration of the memory system A20described above with reference to FIG. 1 is shown.

First, the controller A30 included in the memory system A20 controls thefirst to third nonvolatile memory devices A40, A50 and A60 in responseto a request from the host A10. For example, the controller A30 providesdata read from the first to third nonvolatile memory devices A40, A50and A60, to the host A10, and stores data provided from the host A10, inthe first to third nonvolatile memory devices A40, A50 and A60. To thisend, the controller A30 controls the operations of the first to thirdnonvolatile memory devices A40, A50 and A60, such as read, write,program and erase operations.

In detail, the controller A30 included in the memory system A20 includesa host interface (HOST INTERFACE) 132, a processor (PROCESSOR) 134, amemory 144, a first memory interface (MEMORY INTERFACE1) B10, a secondmemory interface (MEMORY INTERFACE2) B20 and a third memory interface(MEMORY INTERFACE3) B30.

The host interface 132 performs an operation of exchanging commands anddata to be transferred between the controller A30 and the host A10, andmay be configured to communicate with the host A10 through at least oneof various interface protocols such as universal serial bus (USB),multimedia card (MMC), peripheral component interconnect-express(PCI-E), serial attached SCSI (SAS), serial advanced technologyattachment (SATA), parallel advanced technology attachment (DATA), smallcomputer system interface (SCSI), enhanced small disk interface (ESDI),integrated drive electronics (IDE) and MIPI (mobile industry processorinterface). The host interface 32 may be driven through firmware whichis referred to as a host interface layer (HIL), as a region whichexchanges data with the host A10.

The first to third memory interfaces 610, 620 and B30 serve asmemory/storage interfaces which perform interfacing between thecontroller A30 and the first to third nonvolatile memory devices A40,A50 and A60, to allow the controller A30 to control the respective firstto third nonvolatile memory devices A40, A50 and A60 in response to arequest from the host A10. Each of the first to third memory interfaces610, 620 and 630 generates control signals for controlling each of thefirst to third nonvolatile memory devices A40, A50 and A60 and processesdata under the control of the processor 134, as a NAND flash controller(NFC) in the case where each of the first to third nonvolatile memorydevices A40, A50 and A60 is a flash memory, in particular, a NAND flashmemory.

Each of the first to third memory interfaces B10, B20 and B30 maysupport the operation of an interface which processes a command and databetween the controller A30 and each of the first to third nonvolatilememory devices A40, A50 and A60, for example, a NAND flash interface, inparticular, data input/output between the controller A30 and each of thefirst to third nonvolatile memory devices A40, A50 and A60, and may bedriven through firmware which is referred to as a flash interface layer(FIL), as a region which exchanges data with each of the first to thirdnonvolatile memory devices A40, A50 and A60.

The memory 144 as the working memory of the memory system A20 and thecontroller A30 stores data for driving of the memory system A20 and thecontroller A30. In detail, the memory 144 temporarily stores data whichshould be managed, when the controller A30 controls the first to thirdnonvolatile memory devices A40, A50 and A60 in response to a requestfrom the host A10, for example, when the controller A30 controls theoperations of the first to third nonvolatile memory devices A40, A50 andA60, such as read, write, program and erase operations.

The memory 144 may be realized by a volatile memory. For example, thememory 144 may be realized by a static random access memory (SRAM) or adynamic random access memory (DRAM).

The memory 144 may be disposed inside the controller A30 as illustratedin FIG. 2, or may be disposed outside the controller A30. In the casewhere the memory 144 is disposed outside the controller A30, the memory144 should be realized by an external volatile memory to and from whichdata are inputted and outputted from and to the controller A30 through aseparate memory interface (not shown).

The memory 144 stores data which should be managed in the course ofcontrolling the operations of the first to third nonvolatile memorydevices A40, A50 and A60. For such data storage, the memory 144 mayinclude a program memory, a data memory, a write buffer/cache, a readbuffer/cache, a data buffer/cache, a map buffer/cache, and the like.

The memory 144 described in FIG. 2 corresponds to the volatile memory144 described above with reference to FIG. 1. In this regard, thevolatile memory 144 described above with reference to FIG. 1 includesonly a role as a write buffer among the roles of the memory 144described in FIG. 2. Thus, as described above for the volatile memory144 in FIG. 1, the normal write buffer A31, the first write buffer A32and the second write buffer A33 are included in the memory 144 shown inFIG. 2.

The processor 134 controls the operations of the controller A30, and inparticular, controls a program operation or a read operation for thefirst to third nonvolatile memory devices A40, A50 and A60, in responseto a write request or a read request from the host A10. The processor134 drives firmware which is referred to as a flash translation layer(PTL), to control general operations of the controller A30 for the firstto third nonvolatile memory devices A40, A50 and A60. The processor 134may be realized by a microprocessor or a central processing unit (CPU).

For instance, the controller A30 performs an operation requested fromthe host A10, in the first to third nonvolatile memory devices A40, A50and A60, that is, performs a command operation corresponding to acommand received from the host A10, with the first to third nonvolatilememory devices A40, A50 and A60, through the processor 134. Thecontroller A30 may perform a foreground operation as a command operationcorresponding to a command received from the host A10, for example, aprogram operation corresponding to a write command, a read operationcorresponding to a read command, an erase operation corresponding to anerase command or a parameter set operation corresponding to a setparameter command or a set feature command as a set command.

The controller A30 may perform a background operation for the first tothird nonvolatile memory devices A40, A50 and A60, through the processor134. The background operation for the first to third nonvolatile memorydevices A40, A50 and A60 may include an operation of copying data storedin a memory block among memory blocks MEMORY BLOCK<0, 1, 2, . . . > ofthe first to third nonvolatile memory devices A40, A50 and A60, toanother memory block, for example, a garbage collection (GC) operation.The background operation for the first to third nonvolatile memorydevices A40, A50 and A60 may include an operation of swapping storeddata among the memory blocks MEMORY BLOCK<0, 1, 2, . . . > of the firstto third nonvolatile memory devices A40, A50 and A60, for example, awear leveling (WL) operation. The background operation for the first tothird nonvolatile memory devices A40, A50 and A60 may include anoperation of storing map data stored in the controller A30, in thememory blocks MEMORY BLOCK<0, 1, 2, . . . > of the first to thirdnonvolatile memory devices A40, A50 and A60, for example, a map flushoperation. The background operation for the first to third nonvolatilememory devices A40, A50 and A60 may include a bad block managementoperation for the first to third nonvolatile memory devices A40, A50 andA60, for example, checking and processing a bad block among theplurality of memory blocks MEMORY BLOCK<0, 1, 2, . . . > included in thefirst to third nonvolatile memory devices A40, A50 and A60.

The controller A30 may generate and manage log data in correspondence toan operation of accessing the memory blocks MEMORY BLOCK<0, 1, 2, . .. > of the first to third nonvolatile memory devices A40, A50 and A60,through the processor 134. The operation of accessing the memory blocksMEMORY BLOCK<0, 1, 2, . . . > of the first to third nonvolatile memorydevices A40, A50 and A60 includes performing of a foreground operationor a background operation for the memory blocks MEMORY BLOCK<0, 1, 2, .. . > of the first to third nonvolatile memory devices A40, A50 and A60.

In the processor 134 of the controller A30, a unit (not shown) forperforming bad block management of the first to third nonvolatile memorydevices A40, A50 and A60 may be included. Such unit performs a bad blockmanagement of identifying a bad block among the plurality of memoryblocks MEMORY BLOCK<0, 1, 2, . . . > included in the first to thirdnonvolatile memory devices A40, A50 and A60 and processing theidentified bad block as bad. The bad block management means that, in thecase where the first to third nonvolatile memory devices A40, A50 andA60 is a flash memory, for example, a NAND flash memory, since a programfailure may occur when writing data, for example, programming data, dueto the characteristic of the NAND flash memory, a memory block where theprogram failure has occurred is processed as bad and program-failed datais written, that is, programmed, in a new memory block.

The controller A30 performs an operation of transmitting a command anddata to be inputted/outputted between the controller A30 and the firstto third nonvolatile memory devices A40, A50 and A60, through theprocessor 134. The command and data to be inputted/outputted between thecontroller A30 and the first to third nonvolatile memory devices A40,A50 and A60 may be transmitted from the host A10 to the controller A30or may be generated inside the controller A30.

The controller A30 may perform, through the processor 134, the hostinterface 132 and the memory 144 described above, an operation ofchecking whether the write data WDATA inputted from the host A10 aregrouped into a transaction and thereby classifying the normal write dataNMAL_WDATA which are not grouped into a transaction and the first writedata TRAN_WDATA1 and the second write data TRAN_WDATA2 which are groupedinto transactions.

Also, the controller A30 may perform, through the processor 134, thehost interface 132 and the memory 144 described above, an operation ofallocating the normal write buffer A31 for temporarily storing thenormal write data NMAL_WDATA not grouped into a transaction, in thememory 144.

Moreover, the controller A30 may perform, through the processor 134, thehost interface 132 and the memory 144 described above, an operation ofchecking the first total size information TTSIZE1 inputted together withthe first write data TRAN_WDATA1 grouped into the first transaction andthereby allocating the first write buffer A32 for temporarily storingthe first write data TRAN_WDATA1, in the memory 144.

In addition, the controller A30 may perform, through the processor 134,the host interface 132 and the memory 144 described above, an operationof checking the second total size information TTSIZE2 inputted togetherwith the second write data TRAN_WDATA2 grouped into the secondtransaction and thereby allocating the second write buffer A33 fortemporarily storing the second write data TRAN_WDATA2, in the memory144.

The first to third nonvolatile memory devices A40, A50 and A60 in thememory system A20 may retain stored data even though power is notsupplied. In particular, the first to third nonvolatile memory devicesA40, A50 and A60 in the memory system A20 may store write data WDATAprovided from the host A10, through a write operation, and may provideread data (not shown) stored therein, to the host A10, through a readoperation.

While the first to third nonvolatile memory devices A40, A50 and A60 maybe realized by a nonvolatile memory such as a flash memory, for example,a NAND flash memory, it is to be noted that the first to thirdnonvolatile memory devices A40, A50 and A60 may be realized by any onememory among memories such as a phase change memory (phase change randomaccess memory (PCRAM)), a resistive memory (resistive random accessmemory (RRAM (ReRAM))), a ferroelectric memory (ferroelectric randomaccess memory (FRAM)) and a spin transfer torque magnetic memory(STT-RAM: spin transfer torque magnetic random access memory(STT-MRAM)).

The first to third nonvolatile memory devices A40, A50 and A60 includesthe plurality of memory blocks MEMORY BLOCK<0, 1, 2, . . . >. In otherwords, the first to third nonvolatile memory devices A40, A50 and A60may store write data WDATA provided from the host A10, in the memoryblocks MEMORY BLOCK<0, 1, 2, . . . >, through a write operation, and mayprovide read data (not shown) stored in the memory blocks MEMORYBLOCK<0, 1, 2, . . . >, to the host A10, through a read operation.

Each of the memory blocks MEMORY BLOCK<0, 1, 2, . . . > included in thefirst to third nonvolatile memory devices A40, A50 and A60 includes aplurality of pages P<0, 1, 2, 3, 4, . . . >. Also, while not shown indetail in the drawing, a plurality of memory cells are included in eachof the pages P<0, 1, 2, 3, 4, . . . >.

Each of the memory blocks MEMORY BLOCK<0, 1, 2, . . . > included in thefirst to third nonvolatile memory devices A40, A50 and A60 may be asingle level cell (SLC) memory block or a multi-level cell (MLC) memoryblock, depending on the number of bits which may be stored or expressedin one memory cell included therein. An SLC memory block includes aplurality of pages which are realized by memory cells each storing 1bit, and has excellent data computation performance and high durability.An MLC memory block includes a plurality of pages which are realized bymemory cells each storing multi-bit data (for example, 2 or more bits),and may be more highly integrated than the SLC memory block since it hasa larger data storage space than the SLC memory block.

In particular, the MLC memory block may be an MLC memory block includinga plurality of pages which are realized by memory cells each capable ofstoring 2-bit data, a triple level cell (TLC) memory block including aplurality of pages which are realized by memory cells each capable ofstoring 3-bit data, a quadruple level cell (QLC) memory block includinga plurality of pages which are realized by memory cells each capable ofstoring 4-bit data or a multiple level cell memory block including aplurality of pages which are realized by memory cells each capable ofstoring 5 or more-bit data.

FIGS. 3A to 3D and 4A to 4D are diagrams to assist in the explanation ofthe operation of the memory system in accordance with the firstembodiment of the present disclosure.

First, a scheme in which the controller A30 classifies the write dataWDATA inputted from the host A10 into the normal write data NMAL_WDATA,the first write data TRAN_WDATA1 and the second write data TRAN_WDATA2will be described below.

In detail, when the write data WDATA are inputted to the memory systemA20 from the host A10, write commands (not shown) respectivelycorresponding to pieces or items of the write data WDATA are inputtedtogether, and transaction information (not shown) of the write dataWDATA are included in the write commands, respectively.

In the transaction information of each of the write data WDATA,transaction ID (identification) information TRID, transaction commitinformation (not shown) and transaction abort information (not shown)may be included.

Therefore, the controller A30 included in the memory system A20 maycheck transaction ID information TRID in the transaction informationincluded in the write commands, and thereby, may classify the write dataWDATA, which are not grouped into a transaction, into the normal writedata NMAL_WDATA, or the transaction write data TRAN_WDATA1 orTRAN_WDATA2 which are grouped into a transaction.

For example, the controller A30 may classify write data WDATA of whichtransaction ID information TRID have the value of 1, among the writedata WDATA inputted from the host A10, into the first write dataTRAN_WDATA1.

Similarly, the controller A30 may classify write data WDATA of whichtransaction ID information TRID have the value of 2, among the writedata WDATA inputted from the host A10, into the second write dataTRAN_WDATA2.

Also, the controller A30 may classify write data WDATA of whichtransaction ID information TRID are not set to any value, among thewrite data WDATA inputted from the host A10, into the normal write dataNMAL_WDATA.

For reference, the fact that transaction ID information TRID are not setto any value may mean a case where they are set to a defined initialvalue or a value that is meaningless as a transaction ID information.

In a first write command corresponding to start data of the write dataTRAN_WDATA1 or TRAN_WDATA2 which are grouped into a transaction, thereis additionally included the total size information TTSIZE1 or TTSIZE2on a total size of the write data TRAN_WDATA1 or TRAN_WDATA2.

For example, in a first write command corresponding to start data of thefirst write data TRAN_WDATA1 which are grouped into the firsttransaction, there is additionally included the first total sizeinformation TTSIZE1 on a total size of the first write data TRAN_WDATA1.

Because of this fact, the controller A30 may check the first total sizeinformation TTSIZE1 by checking the first write command before the startdata to be inputted first among the first write data TRAN_WDATA1 isinputted from the host A10.

That is, the controller A30 may check the first determined size of thefirst write data TRAN_WDATA1, by checking the first total sizeinformation TTSIZE1 before the first write data TRAN_WDATA1 are inputtedfrom the host A10, and may allocate the first write buffer A32 by anamount of the first determined size in the volatile memory 144.

Thus, the controller A30 may allocate a memory region of the firstdetermined size as the first write buffer A32 in the volatile memory144, and then, may store the first write data TRAN_WDATA1 in the firstwrite buffer A32.

Similarly, in a second write command corresponding to start data of thesecond write data TRAN_WDATA2 which are grouped into the secondtransaction, there is additionally included the second total sizeinformation TTSIZE2 on a total size of the second write dataTRAN_WDATA2.

Because of this fact, the controller A30 may check the second total sizeinformation TTSIZE2 by checking the second write command before thestart data to be inputted first among the second write data TRAN_WDATA2is inputted from the host A10.

That is, the controller A30 may check the second determined size of thesecond write data TRAN_WDATA2, by checking the second total sizeinformation TTSIZE2 before the second write data TRAN_WDATA2 areinputted from the host A10, and may allocate the second write buffer A33by an amount of the second determined size in the volatile memory 144.

Thus, the controller A30 may allocate a memory region of the seconddetermined size as the second write buffer A33 in the volatile memory144, and then, may store the second write data TRAN_WDATA2 in the secondwrite buffer A33.

As described above, the controller A30 allocates the normal write bufferA31, the first write buffer A32 and the second write buffer A33 in thevolatile memory 144. Then, at a specific time, the controller A30flushes data from the normal write buffer A31, the first write bufferA32 and the second write buffer A33 into the nonvolatile memory devicesA40, A50 and A60, through a flush operation for each of the normal writebuffer A31, the first write buffer A32 and the second write buffer A33.

First, in the case of the normal write buffer A31, since it has astorage space which is fixed to the set size, the controller A30performs a flush operation for the normal write buffer A31 at a timewhen the normal write data NMAL_WDATA are stored by the set size in thenormal write buffer A31, and thereby, performs a normal write operationof storing the normal write data NMAL_WDATA stored in the normal writebuffer A31, in the nonvolatile memory devices A40, A50 and A60.

In the case of the first write buffer A32, since it has the storagespace of the first determined size corresponding to the first total sizeinformation TTSIZE1, the controller A30 checks whether the commit of thefirst write data TRAN_WDATA1 is completed or not, at a time when thefirst write data TRAN_WDATA1 are stored by the first predetermined sizein the first write buffer A32. As a result of the checking, in the casewhere the commit of the first write data TRAN_WDATA1 stored in the firstwrite buffer A32 is completed, the controller A30 performs a first flushoperation for the first write buffer A32, and thereby, performs a firstwrite operation of storing the first write data TRAN_WDATA1 stored inthe first write buffer A32, in the nonvolatile memory devices A40, A50and A60. After performing the first write operation, the controller A30releases the first write buffer A32 in the volatile memory 144.

The controller A30 checks whether the first write data TRAN_WDATA1 areaborted or not, at each determined time, even before the first writedata TRAN_WDATA1 are stored by the first determined size in the firstwrite buffer A32. As a result of the checking, in the case where thefirst write data TRAN_WDATA1 stored in the first write buffer A32 areaborted, the controller A30 releases the first write buffer A32 in thevolatile memory 144. The determined time at which whether the firstwrite data TRAN_WDATA1 are aborted is checked may be a time at whicheach of the first write data TRAN_WDATA1 is inputted to the first writebuffer A32.

In the case of the second write buffer A33, since it has the storagespace of the second determined size corresponding to the second totalsize information TTSIZE2, the controller A30 checks whether the commitof the second write data TRAN_WDATA2 is completed or not, at a time whenthe second write data TRAN_WDATA2 are stored by the second determinedsize in the second write buffer A33. As a result of the checking, in thecase where the commit of the second write data TRAN_WDATA2 stored in thesecond write buffer A33 is completed, the controller A30 performs asecond flush operation for the second write buffer A33, and thereby,performs a second write operation of storing the second write dataTRAN_WDATA2 stored in the second write buffer A33, in the nonvolatilememory devices A40, A50 and A60. After performing the second writeoperation, the controller A30 releases the second write buffer A33 inthe volatile memory 144.

The controller A30 checks whether the second write data TRAN_WDATA2 areaborted or not, at each determined time, even before the second writedata TRAN_WDATA2 are stored by the second determined size in the secondwrite buffer A33. As a result of the checking, in the case where thesecond write data TRAN_WDATA2 stored in the second write buffer A33 areaborted, the controller A30 releases the second write buffer A33 in thevolatile memory 144. The determined time at which whether the secondwrite data TRAN_WDATA2 are aborted is checked may be a time at whicheach of the second write data TRAN_WDATA2 is inputted to the secondwrite buffer A33.

In the case where a time at which the commit of the first transaction ischecked and a time at which the commit of the second transaction ischecked are within a set first time interval, the controller A30synchronizes a time at which the first flush operation is performed forthe first write buffer A32 in correspondence to the commit of the firsttransaction and a time at which the second flush operation is performedfor the second write buffer A33 in correspondence to the commit of thesecond transaction.

In the case where a performance time of the first flush operation and aperformance time of the second flush operation are synchronized, thatmeans that a time at which the performance of the first write operationof storing the first write data TRAN_WDATA1 stored in the first writebuffer A32 in the nonvolatile memory devices A40, A50 and A60 is startedand a time at which the performance of the second write operation ofstoring the second write data TRAN_WDATA2 stored in the second writebuffer A33 in the nonvolatile memory devices A40, A50 and A60 is startedare synchronized. Hence, there is a high possibility that a time atwhich the performance of the first write operation is completed and atime at which the performance of the second write operation is completeddo not have a large difference.

Thus, in the case where a performance time of the first flush operationand a performance time of the second flush operation are synchronized,the controller A30 may synchronize a time at which a firstacknowledgement signal for notifying the host A10 that the performanceof the first write operation linked to, and following, the first flushoperation is completed is transferred to the host A10 and a time atwhich a second acknowledgement signal for notifying the host A10 thatthe performance of the second write operation linked to, and following,the second flush operation is completed is transferred to the host A10.

Of course, even in the case where a performance time of the first flushoperation and a performance time of the second flush operation aresynchronized, there may be a case where a time at which the performanceof the first write operation is completed and a time at which theperformance of the second write operation is completed have a largedifference.

Thus, even in the case where a performance time of the first flushoperation and a performance time of the second flush operation aresynchronized, the controller A30 may synchronize, only in the case wherea time at which a first acknowledgement signal for notifying the hostA10 that the performance of the first write operation linked to thefirst flush operation is completed is generated and a time at which asecond acknowledgement signal for notifying the host A10 that theperformance of the second write operation linked to the second flushoperation is completed is generated are within a set second timeinterval, a time at which the first acknowledgement signal istransferred to the host A10 and a time at which the secondacknowledgement signal is transferred to the host A10.

In summary, the controller A30 may perform a first synchronizationoperation of synchronizing a time at which the first acknowledgementsignal is transferred to the host A10 and a time at which the secondacknowledgement signal is transferred to the host A10, by checking onlywhether a performance time of the first flush operation and aperformance time of the second flush operation are synchronized.

Also, the controller A30 may perform a second synchronization operationof synchronizing a time at which the first acknowledgement signal istransferred to the host A10 and a time at which the secondacknowledgement signal is transferred to the host A10, only in the casewhere a time at which the first acknowledgement signal is generated anda time at which the second acknowledgement signal is generated arewithin the set second time interval, even in the case where aperformance time of the first flush operation and a performance time ofthe second flush operation are synchronized.

For reference, the first synchronization operation and the secondsynchronization operation are operations that cannot be performedsimultaneously. Therefore, in the case where the controller A30 performsthe first synchronization operation, the second synchronizationoperation is not performed. Conversely, in the case where the controllerA30 performs the second synchronization operation, the firstsynchronization operation is not performed. Whether the controller A30will perform the first synchronization operation or the secondsynchronization operation may be defined in advance depending on memorycharacteristics and a designer's choice.

The set first time interval serving as a reference for determiningwhether to synchronize a performance time of the first flush operationand a performance time of the second flush operation may be defined inadvance depending on the characteristics of a memory system and adesigner's choice.

Similarly, the set second time interval serving as a reference fordetermining whether to synchronize a time at which the firstacknowledgement signal is transferred to the host A10 and a time atwhich the second acknowledgement signal is transferred to the host A10may be defined in advance depending on the characteristics of a memorysystem and a designer's choice.

Referring to FIG. 3A, it may be assumed that total nine pieces of thewrite data WDATA are inputted from the host A10. A sequence in which thenine pieces of the write data WDATA are inputted from the host A10 isnot defined in advance, and it may be assumed that they are inputtedrandomly.

In detail, by checking the respective transaction ID information TRID ofthe nine pieces of the write data WDATA inputted from the host A10, thecontroller A30 classifies three pieces of the first write dataTRAN_WDATA1, two pieces of the second write data TRAN_WDATA2 and fourpieces of the normal write data NMAL_WDATA.

In further detail, the controller A30 determines that, among the ninepieces of the write data WDATA inputted from the host A10, 0, 1 and 2 asthree pieces of the write data WDATA of which transaction ID informationTRID have the value of 1 are write data WDATA which are grouped into thefirst transaction, and classifies them into the first write dataTRAN_WDATA1.

In a first write command (not shown) corresponding to 0 as start dataamong 0, 1 and 2 grouped into the first write data TRAN_WDATA1, thefirst total size information TTSIZE1 is included. Thus, the controllerA30 may check from the first write command corresponding to 0 that thefirst total size information TTSIZE1 is 5. When the first total sizeinformation TTSIZE1 is checked as 5, the controller A30 allocates amemory region for a total of five pieces of the write data in thevolatile memory 144, and manages the memory region as the first writebuffer A32.

That is, the controller A30 may allocate the first write buffer A32which has a space capable of storing five pieces of the write data, inthe volatile memory 144, before 0 as the start data among 0, 1 and 2grouped into the first write data TRAN_WDATA1 is inputted.

After all the nine pieces of the write data WDATA are inputted from thehost A10, the controller A30 may check that only 0, 1 and 2 exist as thefirst write data TRAN_WDATA1 which are grouped into the firsttransaction. In other words, the controller A30 may check that, at atime when the nine pieces of the write data WDATA are inputted from thehost A10, the first transaction is not completely committed yet(Transaction Uncomplete).

In summary, the controller A30 stores 0, 1 and 2 as the three pieces ofthe first write data TRAN_WDATA1 in the first write buffer A32 which hasa space capable of storing a total of five pieces of the write data, andkeeps a space available for two remaining pieces of the write data.

Further, the controller A30 determines that, among the nine pieces ofthe write data WDATA inputted from the host A10, 110 and 111 as twopieces of the write data WDATA of which transaction ID information TRIDhave the value of 2 are write data WDATA which are grouped into thesecond transaction, and classifies them into the second write dataTRAN_WDATA2.

In a second write command (not shown) corresponding to 110 as start databetween 110 and 111 grouped into the second write data TRAN_WDATA2, thesecond total size information TTSIZE2 is included. Thus, the controllerA30 may check from the second write command corresponding to 110 thatthe second total size information TTSIZE2 is 4. When the second totalsize information TTSIZE2 is checked as 4, the controller A30 allocates amemory region for total four pieces of the write data in the volatilememory 144, and manages the memory region as the second write bufferA33.

That is, the controller A30 may allocate the second write buffer A33which has a space capable of storing four pieces of the write data, inthe volatile memory 144, before 110 as the start data between 110 and111 grouped into the second write data TRAN_WDATA2 is inputted.

After all the nine pieces of the write data WDATA are inputted from thehost A10, the controller A30 may check that only 110 and 111 exist asthe second write data TRAN_WDATA2 which are grouped into the secondtransaction. In other words, the controller A30 may check that, at atime when the nine pieces of the write data WDATA are inputted from thehost A10, the second transaction is not completely committed yet(Transaction Uncomplete).

In summary, the controller A30 stores 110 and 111 as the two pieces ofthe second write data TRAN_WDATA2 in the second write buffer A33 whichhas the space capable of storing a total of four pieces of the writedata, and keeps a space available for two remaining pieces of the writedata.

Moreover, the controller A30 determines that, among the nine pieces ofthe write data WDATA inputted from the host A10, A, B, C and D as writedata WDATA of which transaction ID information TRID are not set to anyvalue are write data WDATA which are not grouped into a transaction, andclassifies them into the normal write data NMAL_WDATA.

The transaction ID information TRID included in a write command (notshown) corresponding to A as start data among A, B, C and D grouped intothe normal write data NMAL_WDATA is not set to any value.

Therefore, when it is checked that the transaction ID information TRIDincluded in the write command corresponding to A is not set to anyvalue, the controller A30 allocates a memory region for total 10 piecesof the write data in the volatile memory 144, and manages the memoryregion as the normal write buffer A31,

The reason why the controller A30 allocates a space of the volatilememory 144 for 10 pieces of the write data as the normal write bufferA31 is because the set size as a reference for the normal write bufferA31 is assumed as 10. Hence, in the case where the set size is 20, thecontroller A30 may allocate a space of the volatile memory 144 for 20pieces of the write data as the normal write buffer A31.

In summary, the controller A30 stores A, B, C and D as the four piecesof the normal write data NMAL_WDATA in the normal write buffer A31 whichhas the space capable of storing a total of 10 pieces of the write data,and keeps a space available for six remaining pieces of the write dataempty.

In the state of FIG. 3A in which the nine pieces of the write data WDATAare inputted as described above, since the normal write data NMAL_WDATAare not full in the normal write buffer A31, it is not a case in whichthe normal write buffer A31 should be flushed. Similarly, since none ofthe first transaction and the second transaction are completed, it isnot a case in which the first write buffer A32 and the second writebuffer A33 should be flushed.

Referring to FIG. 3B in succession to the state shown in FIG. 3A, it maybe assumed that total eight pieces of the write data WDATA are inputtedfrom the host A10. A sequence in which the eight pieces of the writedata WDATA are inputted from the host A10 is not defined in advance, andit may be assumed that they are inputted randomly.

In detail, by checking the respective transaction ID information TRID ofthe eight pieces of the write data WDATA inputted from the host A10, thecontroller A30 classifies two pieces of the first write dataTRAN_WDATA1, two pieces of the second write data TRAN_WDATA2 and fourpieces of the normal write data NMAL_WDATA.

In further detail, the controller A30 determines that, among the eightpieces of the write data WDATA inputted from the host A10, 3 and 4 astwo pieces of the write data WDATA of which transaction ID informationTRID have the value of 1 are write data WDATA which are grouped into thefirst transaction, and classifies them into the first write dataTRAN_WDATA1.

The first write buffer A32 for storing the first write data TRAN_WDATA1which are grouped into the first transaction has already been allocatedin the volatile memory 144 through the operation described above withreference to FIG. 3A.

Therefore, the controller A30 immediately stores 3 and 4 grouped intothe first write data TRAN_WDATA1 in the first write buffer A32 without aseparate additional operation. Through the operation described abovewith reference to FIG. 3A, the first write buffer A32 has been allocatedin the volatile memory 144 as the space capable of storing a total offive pieces of the write data, has stored only 0, 1 and 2 as threepieces of the write data, and has kept space available for two otherpieces of the write data.

Because of this fact, the controller A30 immediately stores 3 and 4grouped into the first write data TRAN_WDATA1 in the first write bufferA32 without a separate additional operation, as in FIG. 3B. As 3 and 4grouped into the first write data TRAN_WDATA1 are stored in the firstwrite buffer A32 in FIG. 3B, the entire space of the first write bufferA32, that is, the space capable of storing five pieces of the writedata, becomes full.

At a time when the entire space of the first write buffer A32 becomesfull as all of 0, 1, 2, 3 and 4 as the first write data TRAN_WDATA1grouped into the first transaction are stored in the first write bufferA32, the controller A30 may check that it is a state in which the commitof the first transaction is completed (Transaction Complete).

Further, the controller A30 determines that, among the eight pieces ofthe write data WDATA inputted from the host A10, 112 and 113 as twopieces of the write data WDATA of which transaction ID information TRIDhave the value of 2 are write data WDATA which are grouped into thesecond transaction, and classifies them into the second write dataTRAN_WDATA2.

The second write buffer A33 for storing the second write dataTRAN_WDATA2 which are grouped into the second transaction has alreadybeen allocated in the volatile memory 144 through the operationdescribed above with reference to FIG. 3A.

Therefore, the controller A30 immediately stores 112 and 113 groupedinto the second write data TRAN_WDATA2 in the second write buffer A33without a separate additional operation. Through the operation describedabove with reference to FIG. 3A, the second write buffer A33 has beenallocated in the volatile memory 144 as the space capable of storingtotal four pieces of the write data, has stored only 110 and 111 as twopieces of the write data, and has kept the space available for storingtwo other pieces of the write data.

Because of this fact, the controller A30 immediately stores 112 and 113grouped into the second write data TRAN_WDATA2 in the second writebuffer A33 without a separate additional operation, as in FIG. 3B. As112 and 113 grouped into the second write data TRAN_WDATA2 are stored inthe second write buffer A33 in FIG. 3B, the entire space of the secondwrite buffer A33, that is, the space capable of storing four pieces ofthe write data, becomes full.

At a time when the entire space of the second write buffer A33 becomesfull as all of 110, 111, 112 and 113 as the second write dataTRAN_WDATA2 grouped into the second transaction are stored in the secondwrite buffer A33, the controller A30 may check that it is a state inwhich the commit of the second transaction is completed (TransactionComplete).

Moreover, the controller A30 determines that, among the eight pieces ofthe write data WDATA inputted from the host A10, E, F, G and H as writedata WDATA of which transaction ID information TRID are not set to anyvalue are write data WDATA which are not grouped into a transaction, andclassifies them into the normal write data NMAL_WDATA.

The normal write buffer A31 for storing the normal write data NMAL_WDATAwhich are not grouped into a transaction has already been allocated inthe volatile memory 144 through the operation described above withreference to FIG. 3A.

Therefore, the controller A30 immediately stores E, F, G and H groupedinto the normal write data NMAL_WDATA in the normal write buffer A31without a separate additional operation. Through the operation describedabove with reference to FIG. 3A, the normal write buffer A31 has beenallocated in the volatile memory 144 as the space capable of storingtotal 10 pieces of the write data, has stored only A, B, C and D as fourpieces of the write data, and has kept a space available for storing sixpieces of the write data.

Because of this fact, the controller A30 immediately stores E, F, G andH grouped into the normal write data NMAL_WDATA in the normal writebuffer A31 without a separate additional operation, as in FIG. 3B. As E,F, G and H grouped into the normal write data NMAL_WDATA are stored inthe normal write buffer A31 in FIG. 3B, A, B, C, D, E, F, G and H aseight pieces of the normal write data NMAL_WDATA are stored in thenormal write buffer A31 which has the space capable of storing total 10pieces of the write data, and an empty space available for storing tworemaining pieces of the normal write data NMAL_WDATA.

In the state of FIG. 3B in succession to the state shown in FIG. 3A, inwhich the eight pieces of the write data WDATA are additionallyinputted, since the normal write data NMAL_WDATA are not full in thenormal write buffer A31, it is not a case in which the normal writebuffer A31 should be flushed. However, since both the first transactionand the second transaction are commit-completed, it is a case in whichthe first write buffer A32 and the second write buffer A33 should beflushed.

When the state shown in FIG. 3A is changed to the state shown in FIG.3B, since it is assumed that an input sequence of the write data WDATAinputted from the host A10 is random, a time at which the commit of thefirst transaction is completed may precede a time at which the commit ofthe second transaction is completed, or a time at which the commit ofthe second transaction is completed may precede a time at which thecommit of the first transaction is completed.

In the case where a time at which the commit of the first transaction iscompleted precedes a time at which the commit of the second transactionis completed, it may be assumed that the commit of the secondtransaction is completed within the set first time interval from thetime at which the commit of the first transaction is completed.

Conversely, in the case where a time at which the commit of the secondtransaction is completed precedes a time at which the commit of thefirst transaction is completed, it may be assumed that the commit of thefirst transaction is completed within the set first time interval fromthe time at which the commit of the second transaction is completed.

In this way, in the case where difference between a time at which thecommit of the first transaction is completed and a time at which thecommit of the second transaction is completed are within the set firsttime interval, the controller A30 synchronizes a time at which a firstflush operation FLUSH1 is performed for the first write buffer A32 incorrespondence to the commit of the first transaction and a time atwhich a second flush operation FLUSH2 is performed for the second writebuffer A33 in correspondence to the commit of the second transaction.

In this way, by synchronizing a performance time of the first flushoperation FLUSH1 and a performance time of the second flush operationFLUSH2, it may be regarded that a time at which the performance of afirst write operation WRITE1 of storing the first write data TRAN_WDATA1stored in the first write buffer A32 in the nonvolatile memory devicesA40, A50 and A60 is started and a time at which the performance of asecond write operation WRITE2 of storing the second write dataTRAN_WDATA2 stored in the second 1write buffer A33 in the nonvolatilememory devices A40, A50 and A60 is started are synchronized.

Accordingly, as in the case of a first synchronization operation shownin FIG. 4A, the controller A30 may synchronize, when a performance timeof the first flush operation FLUSH1 and a performance time of the secondflush operation FLUSH2 are synchronized, a time at which a firstacknowledgement signal ACK1 for notifying the host A10 that theperformance of the first write operation WRITE1 linked to the firstflush operation FLUSH1 is completed is transferred to the host A10 and atime at which a second acknowledgement signal ACK2 for notifying thehost A10 that the performance of the second write operation WRITE2linked to the second flush operation FLUSH2 is completed is transferredto the host A10.

Of course, as in the case of a first synchronization operation shown inFIG. 4B, the controller A30 may not synchronize, when a performance timeof the first flush operation FLUSH1 and a performance time of the secondflush operation FLUSH2 are not synchronized, a time at which a firstacknowledgement signal ACK1 for notifying the host A10 that theperformance of the first write operation WRITE1 linked to the firstflush operation FLUSH1 is completed is transferred to the host A10 and atime at which a second acknowledgement signal ACK2 for notifying thehost A10 that the performance of the second write operation WRITE2linked to the second flush operation FLUSH2 is completed is transferredto the host A10.

Also, as in the case of a second synchronization operation shown in FIG.4C, even in the case where a performance time of the first flushoperation FLUSH1 and a performance time of the second flush operationFLUSH2 are synchronized, only in the case where a time at which a firstacknowledgement signal ACK1 for notifying the host A10 that theperformance of the first write operation WRITE1 linked to the firstflush operation FLUSH1 is completed is generated and a time at which asecond acknowledgement signal ACK2 for notifying the host A10 that theperformance of the second write operation WRITE2 linked to the secondflush operation FLUSH2 is completed is generated are within the setsecond time interval, the controller A30 may synchronize a time at whichthe first acknowledgement signal ACK1 is transferred to the host A10 anda time at which the second acknowledgement signal ACK2 is transferred tothe host A10.

Of course, as in the case of a second synchronization operation shown inFIG. 4D, even in the case where a performance time of the first flushoperation FLUSH1 and a performance time of the second flush operationFLUSH2 are synchronized, in the case where a time at which a firstacknowledgement signal ACK1 for notifying the host A10 that theperformance of the first write operation WRITE1 linked to the firstflush operation FLUSH1 is completed is generated and a time at which asecond acknowledgement signal ACK2 for notifying the host A10 that theperformance of the second write operation WRITE2 linked to the secondflush operation FLUSH2 is completed is generated are not within the setsecond time interval, the controller A30 may not synchronize a time atwhich the first acknowledgement signal ACK1 is transferred to the hostA10 and a time at which the second acknowledgement signal ACK2 istransferred to the host A10.

Referring again to FIG. 3B, after completing the performance of thefirst write operation WRITE1, the controller A30 releases the firstwrite buffer A32 in the volatile memory 144 (WRITE BUFFER1 RELEASE).That is, the controller A30 releases the first write buffer A32 which isallocated in the volatile memory 144 when the first write dataTRAN_WDATA1 are inputted from the host A10, in the volatile memory 144after performing the first write operation WRITE1.

Similarly, after completing the performance of the second writeoperation WRITE2, the controller A30 releases the second write bufferA33 in the volatile memory 144 (WRITE BUFFER2 RELEASE). That is, thecontroller A30 releases the second write buffer A33 which is allocatedin the volatile memory 144 when the second write data TRAN_WDATA2 areinputted from the host A10, in the volatile memory 144 after performingthe second write operation WRITE2.

Referring to FIG. 3C in succession to the state shown in FIG. 3A, it maybe assumed that total seven pieces of the write data WDATA are inputtedfrom the host A10. A sequence in which the seven pieces of the writedata WDATA are inputted from the host A10 is not defined in advance, andit may be assumed that they are inputted randomly.

In detail, by checking the respective transaction ID information TRID ofthe seven pieces of the write data WDATA inputted from the host A10, thecontroller A30 classifies one piece of the first write data TRAN_WDATA1,two pieces of the second write data TRAN_WDATA2 and four pieces of thenormal write data NMAL_WDATA.

In further detail, the controller A30 determines that, among the sevenpieces of the write data WDATA inputted from the host A10, 3 as onepiece of the write data WDATA of which transaction ID information TRIDhas the value of 1 is write data WDATA which is grouped into the firsttransaction, and classifies it into the first write data TRAN_WDATA1.

The first write buffer A32 for storing the first write data TRAN_WDATA1which are grouped into the first transaction has already been allocatedin the volatile memory 144 through the operation described above withreference to FIG. 3A.

Therefore, the controller A30 immediately stores 3 grouped into thefirst write data TRAN_WDATA1 in the first write buffer A32 without aseparate additional operation. Through the operation described abovewith reference to FIG. 3A, the first write buffer A32 has been allocatedin the volatile memory 144 as the space capable of storing total fivepieces of the write data, has stored only 0, 1 and 2 as three pieces ofthe write data, and has kept space available for storing two otherpieces of the write data.

Because of this fact, the controller A30 immediately stores grouped intothe first write data TRAN_WDATA1 in the first write buffer A32 without aseparate additional operation, as in FIG. 3C. As 3 grouped into thefirst write data TRAN_WDATA1 is stored in the first write buffer A32 inFIG. 3C, 0, 1, 2 and 3 as four pieces of the first write dataTRAN_WDATA1 are stored in the first write buffer A32 which has the spacecapable of storing total five pieces of the write data, and a spaceavailable for storing one remaining piece of the write data.

As only 0, 1, 2 and 3 as the first write data TRAN_WDATA1 grouped intothe first transaction are stored in the first write buffer A32, thecontroller A30 may check that a remaining space exists in the firstwrite buffer A32 and thus it is a state in which the commit of the firsttransaction is not completed (Transaction Uncomplete).

Further, the controller A30 determines that, among the seven pieces ofthe write data WDATA inputted from the host A10, 112 and 113 as twopieces of the write data WDATA of which transaction ID information TRIDhave the value of 2 are write data WDATA which are grouped into thesecond transaction, and classifies them into the second write dataTRAN_WDATA2.

The second write buffer A33 for storing the second write dataTRAN_WDATA2 which are grouped into the second transaction has alreadybeen allocated in the volatile memory 144 through the operationdescribed above with reference to FIG. 3A.

Therefore, the controller A30 immediately stores 112 and 113 groupedinto the second write data TRAN_WDATA2 in the second write buffer A33without a separate additional operation. Through the operation describedabove with reference to FIG. 3A, the second write buffer A33 has beenallocated in the volatile memory 144 as the space capable of storingtotal four pieces of the write data, has stored only 110 and 111 as twopieces of the write data, and has kept space available for two otherpieces of the write data.

Because of this fact, the controller A30 immediately stores 112 and 113grouped into the second write data TRAN_WDATA2 in the second writebuffer A33 without a separate additional operation, as in FIG. 3C. As112 and 113 grouped into the second write data TRAN_WDATA2 are stored inthe second write buffer A33 in FIG. 3C, the entire space of the secondwrite buffer A33, that is, the space capable of storing four pieces ofthe write data, becomes full.

At a time when the entire space of the second write buffer A33 becomesfull as all of 110, 111, 112 and 113 as the second write dataTRAN_WDATA2 grouped into the second transaction are stored in the secondwrite buffer A33, the controller A30 may check that it is a state inwhich the commit of the second transaction is completed (TransactionComplete).

Moreover, the controller A30 determines that, among the seven pieces ofthe write data WDATA inputted from the host A10, E, F, G and H as writedata WDATA of which transaction ID information TRID are not set to anyvalue are write data WDATA which are not grouped into a transaction, andclassifies them into the normal write data NMAL_WDATA.

The normal write buffer A31 for storing the normal write data NMAL_WDATAwhich are not grouped into a transaction has already been allocated inthe volatile memory 144 through the operation described above withreference to FIG. 3A.

Therefore, the controller A30 immediately stores E, F, G and H groupedinto the normal write data NMAL_WDATA in the normal write buffer A31without a separate additional operation. Through the operation describedabove with reference to FIG. 3A, the normal write buffer A31 has beenallocated in the volatile memory 144 as the space capable of storingtotal 10 pieces of the write data, has stored only A, B, C and D as fourpieces of the write data, and has kept space available for six otherpieces of the write data.

Because of this fact, the controller A30 immediately stores E, F, G andH grouped into the normal write data NMAL_WDATA in the normal writebuffer A31 without a separate additional operation, as in FIG. 3C. As E,F, G and H grouped into the normal write data NMAL_WDATA are stored inthe normal write buffer A31 in FIG. 3C, A, B, C, D, E, F, G and H aseight pieces of the normal write data NMAL_WDATA are stored in thenormal write buffer A31 which has the space capable of storing total 10pieces of the write data, and thus space available for storing tworemaining pieces of the write data.

In the state of FIG. 3C in succession to the state shown in FIG. 3A, inwhich the seven pieces of the write data WDATA are additionallyinputted, since the normal write data NMAL_WDATA are not full in thenormal write buffer A31, it is not a case in which the normal writebuffer A31 should be flushed. Also, since the commit of the firsttransaction is not completed, it is not a case in which the first writebuffer A32 should be flushed. However, since the commit of the secondtransaction is completed, it is a case in which the second write bufferA33 should be flushed.

When the state shown in FIG. 3A is changed to the state shown in FIG.3C, the first transaction maintains a state in which the commit thereofis not completed, and the second transaction is converted into a statein which the commit thereof is completed. Therefore, in the state asshown in FIG. 3C, it may not be seen that the commit of the firsttransaction is to be completed at which time, but it may be seen that atime at which the commit of the second transaction is completed precedesa time at which the commit of the first transaction is completed.Through this, it may be assumed that the commit of the first transactionis not completed within the set first time interval from the time atwhich the commit of the second transaction is completed.

In this way, in the case where a time at which the commit of the firsttransaction is completed and a time at which the commit of the secondtransaction is completed are not within the set first time interval, thecontroller A30 may not synchronize a time at which a first flushoperation FLUSH1 is performed for the first write buffer A32 incorrespondence to the commit of the first transaction and a time atwhich a second flush operation FLUSH2 is performed for the second writebuffer A33 in correspondence to the commit of the second transaction.

In other words, after the second flush operation FLUSH2 for the secondwrite buffer A33 corresponding to the second transaction which iscommit-completed is performed, when the commit of the first transactionis completed at a certain time that is not within the set first timeinterval, the first flush operation FLUSH1 for the first write bufferA32 corresponding to the first transaction may be performed.

In this way, by not synchronizing a performance time of the first flushoperation FLUSH1 and a performance time of the second flush operationFLUSH2, it may be regarded that the controller A30 may not synchronize atime at which the performance of a first write operation WRITE1 ofstoring the first write data TRAN_WDATA1 stored in the first writebuffer A32 in the nonvolatile memory devices A40, A50 and A60 is startedand a time at which the performance of the second write operation WRITE2of storing the second write data TRAN_WDATA2 stored in the second writebuffer A33 in the nonvolatile memory devices A40, A50 and A60 isstarted. Hence, there is a high possibility that a time at which theperformance of the first write operation is completed and a time atwhich the performance of the second write operation is completed have alarge difference.

Thus, as in the case of the first synchronization operation shown inFIG. 4B, the controller A30 may not synchronize, when a performance timeof the first flush operation FLUSH1 and a performance time of the secondflush operation FLUSH2 are not synchronized, a time at which a firstacknowledgement signal ACK1 for notifying the host A10 that theperformance of the first write operation WRITE1 linked to the firstflush operation FLUSH1 is completed is transferred to the host A10 and atime at which a second acknowledgement signal ACK2 for notifying thehost A10 that the performance of the second write operation WRITE2linked to the second flush operation FLUSH2 is completed is transferredto the host A10.

Because it is assumed in FIG. 3C that a performance time of the firstflush operation FLUSH1 and a performance time of the second flushoperation FLUSH2 are not synchronized, it is impossible that the secondsynchronization operation shown in FIGS. 4C and 4D is performed.

Referring again to FIG. 3C, after completing the performance of thesecond write operation WRITE2, the controller A30 releases the secondwrite buffer A33 in the volatile memory 144 (WRITE BUFFER2 RELEASE),That is, the controller A30 releases the second write buffer A33 whichis allocated in the volatile memory 144 when the second write dataTRAN_WDATA2 are inputted from the host A10, in the volatile memory 144after performing the second write operation WRITE2.

Conversely, since it is a state in which the first flush operationFLUSH1 and the following first write operation WRITE1 are not performedfor the first write buffer A32, the first write buffer A32 maycontinuously maintain the state in which it is allocated in the volatilememory 144.

Referring to FIG. 3D in succession to the state shown in FIG. 3A, it maybe assumed that total seven pieces of the write data WDATA are inputtedfrom the host A10. A sequence in which the seven pieces of the writedata WDATA are inputted from the host A10 is not defined in advance, andit may be assumed that they are inputted randomly.

In detail, by checking the respective transaction ID information TRID ofthe seven pieces of the write data WDATA inputted from the host A10, thecontroller A30 classifies one piece of the first write data TRAN_WDATA1,two pieces of the second write data TRAN_WDATA2 and four pieces of thenormal write data NMAL_WDATA.

In further detail, the controller A30 determines that, among the sevenpieces of the write data WDATA inputted from the host A10, 3 as onepiece of the write data WDATA of which transaction ID information TRIDhas the value of 1 is write data WDATA which is grouped into the firsttransaction, and classifies it into the first write data TRAN_WDATA1,

The first write buffer A32 for storing the first write data TRAN_WDATA1which are grouped into the first transaction has already been allocatedin the volatile memory 144 through the operation described above withreference to FIG. 3A.

Therefore, the controller A30 immediately stores 3 grouped into thefirst write data TRAN_WDATA1 in the first write buffer A32 without aseparate additional operation. Through the operation described abovewith reference to FIG. 3A, the first write buffer A32 has been allocatedin the volatile memory 144 as the space capable of storing total fivepieces of the write data, has stored only 0, 1 and 2 as three pieces ofthe write data, and has kept space available for storing two otherpieces of the write data.

Because of this fact, the controller A30 immediately stores 3 groupedinto the first write data TRAN_WDATA1 in the first write buffer A32without a separate additional operation, as in FIG. 3D. As 3 groupedinto the first write data TRAN_WDATA1 is stored in the first writebuffer A32 in FIG. 3D, 0, 1, 2 and 3 as four pieces of the first writedata TRAN_WDATA1 are stored in the first write buffer A32 which has thespace capable of storing a total of five pieces of the write data, andthus a space remains available for storing one remaining piece of thewrite data.

At a time when 0, 2 and 3 as the first write data TRAN_WDATA1 groupedinto the first transaction are stored in the first write buffer A32, thecontroller A30 may receive an information that the first transaction isaborted, from the host A10. For example, after 3 grouped into the firstwrite data TRAN_WDATA1 is stored in the first write buffer A32, aseparate command including the abort information of the firsttransaction may be transmitted from the host A10. According to thisfact, it may be checked that, in a state in which only 0, 1, 2 and 3 asthe first write data TRAN_WDATA1 grouped into the first transaction arestored in the first write buffer A32, the first transaction is aborted(Transaction Abort).

Further, the controller A30 determines that, among the seven pieces ofthe write data WDATA inputted from the host A10, 112 and 113 as twopieces of the write data WDATA of which transaction ID information TRIDhave the value of 2 are write data WDATA which are grouped into thesecond transaction, and classifies them into the second write dataTRAN_WDATA2.

The second write buffer A33 for storing the second write dataTRAN_WDATA2 which are grouped into the second transaction has alreadybeen allocated in the volatile memory 144 through the operationdescribed above with reference to FIG. 3A.

Therefore, the controller A30 immediately stores 112 and 113 groupedinto the second write data TRAN_WDATA2 in the second write buffer A33without a separate additional operation. Through the operation describedabove with reference to FIG. 3A, the second write buffer A33 has beenallocated in the volatile memory 144 as the space capable of storingtotal four pieces of the write data, has stored only 110 and 111 as twopieces of the write data, and has kept space available for storing twoother pieces of the write data.

Because of this fact, the controller A30 immediately stores 112 and 113grouped into the second write data TRAN_WDATA2 in the second writebuffer A33 without a separate additional operation, as in FIG. 3D. As112 and 113 grouped into the second write data TRAN_WDATA2 are stored inthe second write buffer A33 in FIG. 3D, the entire space of the secondwrite buffer A33, that is, the space capable of storing four pieces ofthe write data, becomes full.

At a time when the entire space of the second write buffer A33 becomesfull as all of 110, 111, 112 and 113 as the second write dataTRAN_WDATA2 grouped into the second transaction are stored in the secondwrite buffer A33, the controller A30 may check that it is a state inwhich the commit of the second transaction is completed (TransactionComplete).

Moreover, the controller A30 determines that, among the seven pieces ofthe write data WDATA inputted from the host A10, E, F, G and H as writedata WDATA of which transaction ID information TRID are not set to anyvalue are write data WDATA which are not grouped into a transaction, andclassifies them into the normal write data NMAL_WDATA.

The normal write buffer A31 for storing the normal write data NMAL_WDATAwhich are not grouped into a transaction has already been allocated inthe volatile memory 144 through the operation described above withreference to FIG. 3A.

Therefore, the controller A30 immediately stores E, F, G and H groupedinto the normal write data NMAL_WDATA in the normal write buffer A31without a separate additional operation. Through the operation describedabove with reference to FIG. 3A, the normal write buffer A31 has beenallocated in the volatile memory 144 as the space capable of storingtotal 10 pieces of the write data, has stored only A, B, C and D as fourpieces of the write data, and has kept space available for six otherpieces of the write data.

Because of this fact, the controller A30 immediately stores E, F, G andH grouped into the normal write data NMAL_WDATA in the normal writebuffer A31 without a separate additional operation, as in FIG. 3D. As E,F, G and H grouped into the normal write data NMAL_WDATA are stored inthe normal write buffer A31 in FIG. 3D, A, B, C, D, E, F, G and H aseight pieces of the normal write data NMAL_WDATA are stored in thenormal write buffer A31 which has the space capable of storing total 10pieces of the write data, and a space available for two remaining piecesof the normal write data NMAL_WDATA.

In the state of FIG. 3D in succession to the state shown in FIG. 3A, inwhich the seven pieces of the write data WDATA are additionallyinputted, since the normal write data NMAL_WDATA are not full in thenormal write buffer A31, it is not a case in which the normal writebuffer A31 should be flushed. Also, since the first transaction isaborted, it is not a case in which the first write buffer A32 should beflushed. However, since the commit of the second transaction iscompleted, it is a case in which the second write buffer A33 should beflushed.

When the state shown in FIG. 3A is changed to the state shown in FIG.3D, the first transaction is converted as aborted, and the secondtransaction is converted into a state in which the commit thereof iscompleted. Therefore, in the state as in FIG. 3D, it is impossible thatthe commit of the first transaction is completed. Thus, it may bedetermined that the first transaction is not committed within the setfirst time interval from a time at which the commit of the secondtransaction is completed.

In the case where, the first transaction is aborted separately from thatthe commit of the second transaction is completed, the controller A30releases the first write buffer A32 in the volatile memory 144 incorrespondence to the abort of the first transaction (WRITE BUFFER1RELEASE).

Further, the second flush operation FLUSH2 is performed for only thesecond write buffer A33 in correspondence to that the commit of thesecond transaction is completed, separately from that the firsttransaction is aborted, and accordingly, the second write operationWRITE2 of storing the second write data TRAN_WDATA2 stored in the secondwrite buffer A33 in the nonvolatile memory devices A40, A50 and A60 isperformed.

Since it is assumed in FIG. 3D that a first flush operation FLUSH1 forthe first write buffer A32 is not performed, the first synchronizationoperation and the second synchronization operation shown in FIGS. 4A to4D are not performed.

Referring again to FIG. 3D, after completing the performance of thesecond write operation WRITE2, the controller A30 releases the secondwrite buffer A33 in the volatile memory 144 (WRITE BUFFER2 RELEASE).That is, the controller A30 releases the second write buffer A33 whichis allocated in the volatile memory 144 when the second write dataTRAN_WDATA2 are inputted from the host A10, in the volatile memory 144after performing the second write operation WRITE2.

Conversely, at a time at which the abort of the first transaction ischecked, the controller A30 releases the first write buffer A32 in thevolatile memory 144.

As is apparent from the above descriptions, the memory system A20 inaccordance with the first embodiment of the present disclosure mayallocate, when the first write data TRAN_WDATA1 which are grouped intothe first transaction are inputted from the host A10, the first writebuffer A32 for exclusive use for the first transaction, in the volatilememory 144. Also, the memory system A20 in accordance with the firstembodiment of the present disclosure may allocate, when the second writedata TRAN_WDATA2 which are grouped into the second transaction areinputted from the host A10, the second write buffer A33 for exclusiveuse for the second transaction, in the volatile memory 144. The firstwrite buffer A32 and the second write buffer A33 may be distinguishedfrom each other. Similarly, the first and second write buffers A32 andA33 may be distinguished from the normal write buffer A31 for managingthe normal write data NMAL_WDATA. Through this, the memory system A20 inaccordance with the first embodiment of the present disclosure mayeffectively manage transaction write data.

Further, the memory system A20 in accordance with the first embodimentof the present disclosure synchronizes a time at which a first flushoperation to be performed in the first write buffer A32 is performedwhen the first transaction is committed and a time at which a secondflush operation to be performed in the second write buffer A33 isperformed when the second transaction is committed, to the maximumwithin a possible range. Through this, the first write operation WRITE1of storing the first write data TRAN_WDATA1 stored in the first writebuffer A32 in the nonvolatile memory devices A40, A50 and A60 and thesecond write operation WRITE2 of storing the second write dataTRAN_WDATA2 stored in the second write buffer A33 in the nonvolatilememory devices A40, A50 and A60 may be started by being synchronized,and a possibility to intensively store the first write data TRAN_WDATA1and the second write data TRAN_WDATA2 may be increased by collectivelystoring them in a specific storage space of the nonvolatile memorydevices A40, A50 and A60. Namely, an algorithm for ensuring the firsttransaction and the second transaction may be simplified.

Moreover, the memory system A20 in accordance with the first embodimentof the present disclosure maximally synchronizes, within a possiblerange, times at which the first and second acknowledgement signals ACK1and ACK2 are transmitted to the host A10 to notify the host A10 that thesynchronized first and second write operations WRITE1 and WRITE2 arecompleted when the first and second write buffers A32 and A33 areflushed in a synchronized state. That is, the memory system A20 maytransfer the two acknowledgement signals ACK1 and ACK2 to the host A10at one timing. Through this, the number of times by which anacknowledgement signal is transmitted to the host A10 from the memorysystem A20 may be minimized.

FIGS. 5A to 5C are flow charts to assist in the explanation of theoperation of the memory system in accordance with the first embodimentof the present disclosure.

Referring to FIG. 5A, the operation of the memory system A20 inaccordance with the first embodiment of the present disclosure isstarted when write data WDATA is transmitted from the host A10 to thememory system A20 (S5).

Whether the write data WDATA transmitted at the step S5 is start data ofa transaction is checked (S10).

In the case where the write data WDATA is start data of a transaction atthe step S10 (YES), the memory system A20 generates a dedicatedtransaction write buffer for storing transaction data of the transaction(S20). At the step S20, dedicated transaction write buffers aregenerated by the number of transactions. That is, a first transactionwrite buffer is generated for a first transaction, and a secondtransaction write buffer is generated for a second transaction. At thestep S20, the size of the dedicated transaction write buffer may bedepend on the total size information of the transaction which istransferred together with start data of the transaction.

In the case where the write data WDATA is not start data of atransaction at the step S10 (NO), it may be regarded that the write dataWDATA transmitted at the step S5 is normal write data NMAL_WDATA oranother data other than start data of the transaction.

In the case where the write data WDATA transmitted at the step S5 isnormal write data NMAL_WDATA, the write data WDATA is stored in a normalwrite buffer (530).

In the case where the write data WDATA transmitted at the step S5 isanother data other than start data of the transaction, the write dataWDATA is stored in the transaction write buffer which is generated atthe step S20 (S30). At the step S30, it is checked which kind of atransaction the write data WDATA transmitted at the step S5 is, and thewrite data WDATA is stored in a transaction write buffer correspondingto the checked transaction. In other words, at the step S30, in the casewhere the write data WDATA transmitted at the step S5 is another data ofthe first transaction, the write data WDATA is stored in the firsttransaction write buffer, and, in the case where the write data WDATAtransmitted at the step S5 is another data of the second transaction,the write data WDATA is stored in the second transaction write buffer.

After the step S30, whether a buffer of which commit is completed existsamong transaction write buffers is checked (S40).

In the case where a buffer of which commit is completed does not existat the step S40 (NO), a separate operation is not performed until newwrite data WDATA is inputted at the step S5.

In the case where a buffer of which commit is completed exists at thestep S40 (YES), whether the commit of another transaction is completedis checked (S50). In other words, through the step S40 and the step S50,whether at least two transactions are committed may be checked.

In the case where only one transaction is committed as a result of thestep S50 (NO), only the transaction write buffer which is committed isflushed alone (S80). The transaction write buffer which is flushed atthe step S80 is not flushed simultaneously with another transactionwrite buffer.

In the case where at least two transaction write buffers are committedas a result of the step S50 (YES), whether the commit times of the atleast two transactions are within a set first time interval (SET TIME1)is checked (S60). That is, whether the commit time of a transaction(Transaction WRITE Buffer<S40>) of which commit is checked at the stepS40 and the commit time of a transaction (Transaction WRITE Buffer<S50>)of which commit is checked at the step S50 are within the set first timeinterval (SET TIME1) is checked (S60).

In the case where difference between the commit times of the at leasttwo transactions exceed the set first time interval (SET TIME1) at thestep S60 (NO), flush operations for the at least two transaction writebuffers which are commit-completed are not synchronized (S80). That is,a flush operation for the transaction (Transaction WRITE Buffer<S40>) ofwhich commit is checked at the step S40 and a flush operation for thetransaction (Transaction WRITE Buffer<S50>) of which commit is checkedat the step S50 are not synchronized (S80).

In the case where difference between the commit times of the at leasttwo transaction write buffers are within the set first time interval(SET TIME1) at the step S60 (YES), flush operations for the at least twotransaction write buffers which are commit-completed are synchronized(S70). That is, a flush operation for the transaction (Transaction WRITEBuffer<S40>) of which commit is checked at the step S40 and a flushoperation for the transaction (Transaction WRITE Buffer<S50>) of whichcommit is checked at the step S50 are synchronized (S70).

After the flush operations for the at least two transaction writebuffers which are commit-completed are synchronized at the step S70, anyone operation of two operations may be selected and performed byreferring to FIGS. 5B and 5C as will be described below.

Referring to FIG. 5B, in correspondence to that the flush operations forthe at least two transaction write buffers which are commit-completedare synchronized at the step S70, at least two write operations (Writeto Non-Volatile Memory, Transaction WRITE Buffer <S40 & S50>) of storingthe transaction data stored in the at least two transaction writebuffers, in the nonvolatile memory devices A40, A50 and A60, aresynchronized (S90).

Since the flush operations for the at least two transaction writebuffers which are commit-completed are synchronized and accordingly theat least two write operations are synchronized at the step S70 and thestep S90, in FIG. 5B, a separate condition is not additionally checked,and times at which at least two acknowledgement signals (Ack<S40 & 550>of Write Complete corresponding to (Transaction WRITE) Buffer<S40 &S50>) for notifying the host A10 that the at least two write operationsare completed are transmitted to the host A10 are synchronized (S100),

Referring to FIG. 5C, in correspondence to that the flush operations forthe at least two transaction write buffers which are commit-completedare synchronized at the step S70, at least two write operations (Writeto Non-Volatile Memory, Transaction WRITE Buffer <S40 & S50>) of storingthe transaction data stored in the at least two transaction writebuffers, in the nonvolatile memory devices A40, A50 and A60, aresynchronized (S90).

After the flush operations for the at least two transaction writebuffers which are commit-completed are synchronized and accordingly theat least two write operations are synchronized at the step S70 and thestep S90, in FIG. 5C, whether difference between times at which the atleast two write operations are completed are within a set second timeinterval (SET TIME2) is checked (S110).

In the case where difference between times at which the at least twowrite operations are completed are within the set second time interval(SET TIME2) at the step S110 (YES), times at which at least twoacknowledgement signals (Ack<S40 & S50> of Write Complete correspondingto (Transaction WRITE) Buffer<S40 & S50>) for notifying the host A10that the at least two write operations are completed are transmitted tothe host A10 are synchronized (S120).

In the case where difference between times at which the at least twowrite operations are completed exceed the set second time interval (SETTIME2) at the step S110 (NO), times at which at least twoacknowledgement signals (Ack<S40 & S50> of Write Complete correspondingto (Transaction WRITE) Buffer<S40 & S50>) for notifying the host A10that the at least two write operations are completed are transmitted tothe host A10 are not synchronized (S130).

Second Embodiment

FIGS. 6 and 7 are diagrams to assist in the explanation of theconfiguration of a data processing system including a memory system inaccordance with a second embodiment of the present disclosure.

Referring to FIG. 6, the data processing system in accordance with thesecond embodiment of the present disclosure includes a host C10 and amemory system C20. The memory system C20 includes a controller C30, afirst nonvolatile memory device C40, a second nonvolatile memory deviceC50 and a third nonvolatile memory device C60.

For reference, in FIGS. 6 and 7, three nonvolatile memory devices C40,C50 and C60 are included in the memory system C20. However, this ismerely an example, as previously noted.

The host C10 transmits a plurality of commands corresponding to a userrequest to the memory system C20, and accordingly, the memory system C20performs operations corresponding to the commands, that is, operationscorresponding to the user request.

The memory system C20 operates in response to a request of the host C10,in particular, stores data to be accessed by the host C10. In otherwords, the memory system C20 may be used as a main memory device or anauxiliary memory device of the host C10. The memory system C20 may berealized as any one of various kinds of storage devices, depending on ahost interface protocol which is coupled with the host C10. For example,the memory system C20 may be realized as any of various kinds of storagedevices such as a solid state driver (SSD), a multimedia card in theform of an MMC, an eMMC (embedded MMC), an RS-MMC (reduced size MMC) anda micro-MMC, a secure digital card in the form of an SD, a mini-SD and amicro-SD, a universal serial bus (USB) storage device, a universal flashstorage (UFS) device, a compact flash (CF) card, a smart media card, amemory stick, and the like.

Also, the memory system C20 may be integrated into one semiconductordevice and configure a memory card. For instance, the memory system C20may configure a memory card such as a Personal Computer Memory CardInternational Association (PCMCIA) card, a compact flash (CF) card, asmart media card in the form of an SM and an SMC, a memory stick, amultimedia card in the form of an MMC, an RS-MMC and a micro-MMC, asecure digital card in the form of an SD, a mini-SD, a micro-SD and anSDHC, and a universal flash storage (UFS) device.

For another instance, the memory system C20 may configure a computer, anultra mobile PC (UMPC), a workstation, a net-book, a personal digitalassistant (PDA), a portable computer, a web tablet, a tablet computer, awireless phone, a mobile phone, a smart phone, an e-book, a portablemultimedia player (PMP), a portable game player, a navigation device, ablack box, a digital camera, a digital multimedia broadcasting (DMB)player, a 3-dimensional television, a smart television, a digital audiorecorder, a digital audio player, a digital picture recorder, a digitalpicture player, a digital video recorder, a digital video player, astorage configuring a data center, a device capable of transmitting andreceiving information under a wireless environment, one of variouselectronic devices configuring a home network, one of various electronicdevices configuring a computer network, one of various electronicdevices configuring a telematics network, an RFID (radio frequencyidentification) device, or one of various component elements configuringa computing system.

The memory system C20 may include a storage device such as a volatilememory device such as a dynamic random access memory (DRAM) and a staticrandom access memory (SRAM) or a nonvolatile memory device such as aread only memory (ROM), a mask ROM (MROM), a programmable ROM (PROM), anerasable programmable ROM (EPROM), an electrically erasable andprogrammable ROM (EEPROM), an ferroelectric random access memory (FRAM),a phase change RAM (PRAM), a magnetic RAM (MRAM), a resistive RAM (RRAM)and a flash memory.

The memory system C20 includes a volatile memory 144 for temporarilystoring write data WDATA inputted from the host C10.

The controller C30 allocates a plurality of write buffers C31, C32, C33and C34 each having a predefined size, in the volatile memory 144. Thecontroller C30 stores normal write data NMAL_WDATA which are inputtedfrom the host C10 and are not grouped into a transaction, in writebuffers which are not set for exclusive use for a transaction, among theplurality of write buffers C31, C32, C33 and C34.

When first write data TRAN_WDATA1 which are grouped into a firsttransaction and a first total size information TTSIZE1 on a total sizeof the first transaction are inputted from the host C10, the controllerC30 sets, in response to the first total size information TTSIZE1, afirst exclusive use option for exclusively using at least one firstwrite buffer among the plurality of write buffers C31, C32, C33 and C34,for the first transaction.

In detail, the controller C30 checks respective empty spaces of theplurality of write buffers C31, C32, C33 and C34 at a time when thefirst write data TRAN_WDATA1 are inputted from the host C10, sets thefirst exclusive use option for a minimum number of write buffers whichare combinable among the plurality of write buffers C31, C32, C33 andC34, in response to the checked empty spaces and the first total sizeinformation TTSIZE1, and uses the minimum number of write buffers as thefirst write buffer.

Also, when second write data TRAN_WDATA2 which are grouped into a secondtransaction and a second total size information TTSIZE2 on a total sizeof the second transaction are inputted from the host C10, the controllerC30 sets, in response to the second total size information TTSIZE2, asecond exclusive use option for exclusively using at least one secondwrite buffer among the remaining write buffers except the first writebuffer among the plurality of write buffers C31, C32, C33 and C34, forthe second transaction.

In detail, the controller C30 checks respective empty spaces of theremaining write buffers except the first write buffer among theplurality of write buffers C31, C32, C33 and C34 at a time when thesecond write data TRAN_WDATA2 are inputted from the host C10, sets thesecond exclusive use option for a minimum number of write buffers whichare combinable among the remaining write buffers except the first writebuffer among the plurality of write buffers C31, C32, C33 and C34 inresponse to the checked empty spaces and the second total sizeinformation TTSIZE2, and uses the minimum number of write buffers as thesecond write buffer.

For reference, by assuming that the first write data TRAN_WDATA1 whichare grouped into the first transaction are inputted earlier than thesecond write data TRAN_WDATA2 which are grouped into the secondtransaction, it is assumed that the setting of the first write bufferfor exclusive use for the first transaction precedes the setting of thesecond write buffer for exclusive use for the second transaction.Therefore, when setting the first write buffer, the first write bufferis set by selecting at least one write buffer among the plurality ofwrite buffers C31, C32, C33 and C34, but, when setting the second writebuffer, the second write buffer is set by selecting at least one writebuffer among the remaining write buffers except the write buffer set asthe first write buffer among the plurality of write buffers C31, C32,C33 and C34.

In summary, the controller C30 allocates the plurality of write buffersC31, C32, C33 and C34 in the volatile memory 144 before the write dataWDATA are inputted from the host C10. In this way, the plurality ofwrite buffers C31, C32, C33 and C34 are first allocated in the volatilememory 144. Thereafter, in the case where write data WDATA which aregrouped into a transaction are inputted from the host C10, thecontroller C30 sets at least one write buffer among the plurality ofwrite buffers C31, C32, C33 and C34, for exclusive use for thetransaction, and then, stores the write data WDATA which are groupedinto the transaction, collectively in the write buffer set for exclusiveuse for the transaction. In the case where the normal write dataNMAL_WDATA are inputted from the host C10, the normal write dataNMAL_WDATA are stored by being appropriately distributed over writebuffers which are not set for exclusive use for a transaction, among theplurality of write buffers C31, C32, C33 and C34.

The fact that write data WDATA are grouped into a transaction means thata plurality of write data WDATA used for the same use among write dataWDATA are grouped into one transaction.

For example, in a database, data used for uses such as the correction,addition and update of already stored data may be grouped intorespective transactions according to the respective uses. In thisregard, data of the use for correcting a database may be set to begrouped into one transaction group, and data of the use for adding adatabase may be set to be grouped into another transaction group.

Therefore, when write data TRAN_WDATA1 or TRAN_WDATA2 which are groupedinto one transaction are transmitted from the host C10 to the memorysystem C20, there exists only a commit state in which all the write dataTRAN_WDATA1 or TRAN_WDATA2 are normally transmitted and stored and arethus valid or an abort state in which even any one of the write dataTRAN_WDATA1 or TRAN_WDATA2 is not normally transmitted and stored or allthe write data TRAN_WDATA1 or TRAN_WDATA2 are invalid according to anabort request of the host C10. That is, write data TRAN_WDATA which aregrouped into one transaction are meaningful only when they are in acommit state as all of them are normally transmitted and stored and arethus all valid.

For example, in order for the first write data TRAN_WDATA1 grouped intoa transaction among the write data WDATA transmitted from the host C10to the memory system C20 to be checked as a commit state in the memorysystem C20, all of the plurality of first write data TRAN_WDATA1 shouldbe normally transmitted from the host C10 to the memory system C20 andbe completely stored in the memory system C20, and at the same time,there should be no abort request from the host C10. If even any one ofthe plurality of first write data TRAN_WDATA1 is not normallytransmitted and stored or an abort request is received from the hostC10, all of the first write data TRAN_WDATA1 are checked as an abortstate in the memory system C20.

Similarly, in order for the second write data TRAN_WDATA2 grouped intothe second transaction among the write data WDATA transmitted from thehost C10 to the memory system C20 to be checked as a commit state in thememory system C20, all of the plurality of second write data TRAN_WDATA2should be normally transmitted from the host C10 to the memory systemC20 and be completely stored in the memory system C20, and at the sametime, there should be no abort request from the host C10. If even anyone of the plurality of second write data TRAN_WDATA2 is not normallytransmitted and stored or an abort request is received from the hostC10, all of the second write data TRAN_WDATA2 are checked as an abortedstate in the memory system C20.

For reference, the operation of managing the write data TRAN_WDATA1 orTRAN_WDATA2 grouped into a transaction, by classifying them into acommit state or an aborted state as described above, may be generallyreferred to as an operation for ensuring the transaction.

The reason why the plurality of write buffers C31, C32, C33 and C34allocated in the volatile memory 144 of the controller C30 are shown bythe solid lines in FIG. 6 is because the controller C30 allocates theplurality of write buffers C31, C32, C33 and C34 in the volatile memory144 before the write data WDATA are inputted from the host C10.

The controller C30 sets the plurality of write buffers C31, C32, C33 andC34 by fixing them to the predefined size.

In response to the first total size information TTSIZE1 inputtedtogether with the first write data TRAN_WDATA1 when the first write dataTRAN_WDATA1 grouped into the first transaction are inputted from thehost C10, the controller C30 checks a first determined size for thefirst write data TRAN_WDATA1, and then checks whether a write buffer ofwhich empty space is capable of accommodating the first determined sizeexists among the write buffers C31, C32, C33 and C34 allocated inadvance in the volatile memory 144.

In the case where an empty space capable of accommodating the firstdetermined size exists only in one write buffer among the plurality ofwrite buffers C31, C32, C33 and C34, the first exclusive use option isset for the one write buffer and the one write buffer is selected as thefirst write buffer.

In the case where an empty space capable of accommodating the firstdetermined size exists in each of two or more write buffers among theplurality of write buffers C31, C32, C33 and C34, the first exclusiveuse option is set for a write buffer of which empty space size issmallest, among the two or more write buffers each capable ofaccommodating the first determined size, and the corresponding writebuffer is selected as the first write buffer.

In the case where only the empty space size of any one write bufferamong the plurality of write buffers C31, C32, C33 and C34 cannotaccommodate the first determined size and the size obtained by summingthe empty spaces of at least two write buffers may accommodate the firstdetermined size, the first exclusive use option is set for all of atleast two write buffers of which size obtained by summing their emptyspaces is closest to the first determined size, and the corresponding atleast two write buffers are selected as the first write buffer.

In response to the second total size information TTSIZE2 inputtedtogether with the second write data TRAN_WDATA2 when the second writedata TRAN_WDATA2 grouped into the second transaction are inputted fromthe host C10 after the first write data TRAN_WDATA1 grouped into thefirst transaction are inputted from the host C10, the controller C30checks a second determined size for the second write data TRAN_WDATA2,and then checks whether a write buffer of which empty space is capableof accommodating the second determined size exists among the remainingwrite buffers except the first write buffer among the write buffers C31,C32, C33 and C34 allocated in advance in the volatile memory 144.

In the case where an empty space capable of accommodating the seconddetermined size exists only in one write buffer among the remainingwrite buffers except the first write buffer among the plurality of writebuffers C31, C32, C33 and C34, the second exclusive use option is setfor the one write buffer and the one write buffer is selected as thesecond write buffer.

In the case where an empty space capable of accommodating the seconddetermined size exists in each of two or more write buffers among theremaining write buffers except the first write buffer among theplurality of write buffers C31, C32, C33 and C34, the second exclusiveuse option is set for a write buffer of which empty space size issmallest, among the two or more write buffers each capable ofaccommodating the second determined size, and the corresponding writebuffer is selected as the second write buffer.

In the case where only the empty space size of any one write bufferamong the remaining write buffers except the first write buffer amongthe plurality of write buffers C31, C32, C33 and C34 cannot accommodatethe second determined size and the size obtained by summing the emptyspaces of at least two write buffers may accommodate the seconddetermined size, the second exclusive use option is set for all of atleast two write buffers of which size obtained by summing their emptyspaces is closest to the second determined size, and the correspondingat least two write buffers are selected as the second write buffer.

Referring to FIG. 7, the detailed configuration of the memory system C20described above with reference to FIG. 6 may be seen.

First, the controller C30 included in the memory system C20 controls thefirst to third nonvolatile memory devices C40, C50 and C60 in responseto a request from the host C10. For example, the controller C30 providesdata read from the first to third nonvolatile memory devices C40, C50and C60, to the host C10, and stores data provided from the host C10, inthe first to third nonvolatile memory devices C40, C50 and C60. To thisend, the controller C30 controls the operations of the first to thirdnonvolatile memory devices C40, C50 and C60, such as read, write,program and erase operations.

In detail, the controller C30 included in the memory system C20 includesa host interface (HOST INTERFACE) 132, a processor (PROCESSOR) 134, amemory 144, a first memory interface (MEMORY INTERFACE1) D10, a secondmemory interface (MEMORY INTERFACE2) D20 and a third memory interface(MEMORY INTERFACE3) D30.

The host interface 132 performs an operation of exchanging commands anddata to be transferred between the memory system C20 and the host C10,and may be configured to communicate with the host C10 through at leastone of various interface protocols such as universal serial bus (USB),multimedia card (MMC), peripheral component interconnect-express (PCI-eor PCIe), serial attached SCSI (SAS), serial advanced technologyattachment (SATA), parallel advanced technology attachment (PATA), smallcomputer system interface (SCSI), enhanced small disk interface (ESDI),integrated drive electronics (IDE) and MIPI (mobile industry processorinterface). The host interface 32 may be driven through firmware whichis referred to as a host interface layer (HIL), as a region whichexchanges data with the host C10.

The first to third memory interfaces D10, D20 and D30 serve asmemory/storage interfaces which perform interfacing between thecontroller C30 and the first to third nonvolatile memory devices C40,C50 and C60, to allow the controller C30 to control the respective firstto third nonvolatile memory devices C40, C50 and C60 in response to arequest from the host C10. Each of the first to third memory interfacesD10, D20 and D30 generates control signals for each of the first tothird nonvolatile memory devices C40, C50 and C60 and processes dataunder the control of the processor 134, as a NAND flash controller (NFC)in the case where each of the first to third nonvolatile memory devicesC40, C50 and C60 is a flash memory, in particular, in the case whereeach of the first to third nonvolatile memory devices C40, C50 and C60is a NAND flash memory.

Each of the first to third memory interfaces D10, D20 and D30 maysupport the operation of an interface which processes a command and databetween the controller C30 and each of the first to third nonvolatilememory devices C40, C50 and C60, for example, a NAND flash interface, inparticular, data input/output between the controller C30 and each of thefirst to third nonvolatile memory devices C40, C50 and C60, and may bedriven through firmware which is referred to as a flash interface layer(FIL), as a region which exchanges data with each of the first to thirdnonvolatile memory devices C40, C50 and C60.

The memory 144 as the working memory of the memory system C20 and thecontroller C30 stores data for driving of the memory system C20 and thecontroller C30. In detail, the memory 144 temporarily stores data whichshould be managed, when the controller C30 controls the first to thirdnonvolatile memory devices C40, C50 and C60 in response to a requestfrom the host C10, for example, when the controller C30 controls theoperations of the first to third nonvolatile memory devices C40, C50 andC60, such as read, write, program and erase operations.

The memory 144 may be realized by a volatile memory. For example, thememory 144 may be realized by a static random access memory (SRAM) or adynamic random access memory (DRAM).

The memory 144 may be disposed inside the controller C30 as illustratedin FIG. 7, and may be disposed outside the controller C30. In the casewhere the memory 144 is disposed outside the controller C30, the memory144 should be realized by an external volatile memory to and from whichdata are inputted and outputted from and to the controller C30 through aseparate memory interface (not shown).

The memory 144 stores data which should be managed in the course ofcontrolling the operations of the first to third nonvolatile memorydevices C40, C50 and C60. For such data storage, the memory 144 mayinclude a program memory, a data memory, a write buffer/cache, a readbuffer/cache, a data buffer/cache, a map buffer/cache, and the like.

The memory 144 described in FIG. 7 is a component corresponding to thevolatile memory 144 described above with reference to FIG. 6. In thisregard, the volatile memory 144 described above with reference to FIG. 6includes only a role as a write buffer among the roles of the memory 144described in FIG. 7. Thus, as described above for the volatile memory144 in FIG. 6, the plurality of write buffers C31, C32, C33 and C34 areincluded in the memory 144 shown in FIG. 7.

The processor 134 controls the entire operations of the controller C30,and in particular, controls a program operation or a read operation forthe first to third nonvolatile memory devices C40, C50 and C60, inresponse to a write request or a read request from the host C10. Theprocessor 134 drives firmware which is referred to as a flashtranslation layer (FTL), to control general operations of the controllerC30 for the first to third nonvolatile memory devices C40, C50 and C60.The processor 134 may be realized by a microprocessor or a centralprocessing unit (CPU).

For instance, the controller C30 performs an operation requested fromthe host C10, in the first to third nonvolatile memory devices C40, C50and C60, that is, performs a command operation corresponding to acommand received from the host C10, with the first to third nonvolatilememory devices C40, C50 and C60, through the processor 134. Thecontroller C30 may perform a foreground operation as a command operationcorresponding to a command received from the host C10, for example, aprogram operation corresponding to a write command, a read operationcorresponding to a read command, an erase operation corresponding to anerase command or a parameter set operation corresponding to a setparameter command or a set feature command as a set command.

The controller C30 may perform a background operation for the first tothird nonvolatile memory devices C40, C50 and C60, through the processor134. The background operation for the first to third nonvolatile memorydevices C40, C50 and C60 may include an operation of copying data storedin a certain memory block among memory blocks MEMORY BLOCK<0, 1, 2, . .. > of each of the first to third nonvolatile memory devices C40, C50and C60, to another certain memory block, for example, a garbagecollection (GC) operation. The background operation for the first tothird nonvolatile memory devices C40, C50 and C60 may include anoperation of swapping stored data among the memory blocks MEMORYBLOCK<0, 1, 2, . . . > of each of the first to third nonvolatile memorydevices C40, C50 and C60, for example, a wear leveling (WL) operation.The background operation for the first to third nonvolatile memorydevices C40, C50 and C60 may include an operation of storing map datastored in the controller C30, in the memory blocks MEMORY BLOCK<0, 1, 2,. . . , > of each of the first to third nonvolatile memory devices C40,C50 and C60, for example, a map flush operation. The backgroundoperation for the first to third nonvolatile memory devices C40, C50 andC60 may include a bad block management operation for the first to thirdnonvolatile memory devices C40, C50 and C60, for example, checking andprocessing a bad block among the plurality of memory blocks MEMORYBLOCK<0, 1, 2, . . . > included in each of the first to thirdnonvolatile memory devices C40, C50 and C60.

The controller C30 may generate and manage log data in correspondence toan operation of accessing the memory blocks MEMORY BLOCK<0, 1, 2, . .. > of each of the first to third nonvolatile memory devices C40, C50and C60, through the processor 134. The operation of accessing thememory blocks MEMORY BLOCK<0, 1, 2, . . . > of each of the first tothird nonvolatile memory devices C40, C50 and C60 includes performing ofa foreground operation or a background operation for the memory blocksMEMORY BLOCK<0, 1, 2, . . . > of each of the first to third nonvolatilememory devices C40, C50 and C60.

In the processor 134 of the controller C30, a unit (not shown) forperforming bad block management of the first to third nonvolatile memorydevices C40, C50 and C60 may be included. The unit for performing badblock management performs a bad block management of checking a bad blockamong the plurality of memory blocks MEMORY BLOCK<0, 1, 2, . . . >included in each of the first to third nonvolatile memory devices C40,C50 and C60 and processing the checked bad block as bad. The bad blockmanagement means that, in the case where each of the first to thirdnonvolatile memory devices C40, C50 and C60 is a flash memory, forexample, a NAND flash memory, since a program failure may occur whenwriting data, for example, programming data, due to the characteristicof the NAND flash memory, a memory block where the program failure hasoccurred is processed as bad and program-failed data is written, thatis, programmed, in a new memory block.

The controller C30 performs an operation of transmitting a command anddata to be inputted/outputted between the controller C30 and the firstto third nonvolatile memory devices C40, C50 and C60, through theprocessor 134. The command and data to be inputted/outputted between thecontroller C30 and the first to third nonvolatile memory devices C40,C50 and C60 may be transmitted from the host C1.0 to the controller C30or may be generated inside the controller C30.

The controller C30 may perform, through the processor 134, the hostinterface 132 and the memory 144 described above, an operation ofchecking whether the write data WDATA inputted from the host C10 aregrouped into a transaction and thereby classifying the normal write dataNMAL_WDATA which are not grouped into a transaction and the first writedata TRAN_WDATA1 and the second write data TRAN_WDATA2 which are groupedinto transactions.

Also, the controller C30 may perform, through the processor 134, thehost interface 132 and the memory 144 described above, an operation ofallocating the plurality of write buffers C31, C32, C33 and C34 fortemporarily storing the write data WDATA inputted from the host C10, inthe memory 144.

The controller C30 may temporarily store, through the processor 134 andthe memory 144 described above, the normal write data NMAL WDATA in awrite buffer which are not set for exclusive use for a transaction,among the plurality of write buffers C31, C32, C33 and C34 allocated inthe memory 144.

Moreover, the controller C30 may perform, through the processor 134, thehost interface 132 and the memory 144 described above, an operation ofchecking the first total size information TTSIZE1 inputted together withthe first write data TRAN_WDATA1 grouped into the first transaction,setting at least one first write buffer among the plurality of writebuffers C31, C32, C33 and C34 for exclusive use for the firsttransaction depending on a checking result and thereby temporarilystoring the first write data TRAN_WDATA1.

Further, the controller C30 may perform, through the processor 134, thehost interface 132 and the memory 144 described above, an operation ofchecking the second total size information TTSIZE2 inputted togetherwith the second write data TRAN_WDATA2 grouped into the secondtransaction, setting at least one second write buffer among theremaining write buffers except the first write buffer among theplurality of write buffers C31, C32, C33 and C34 for exclusive use forthe second transaction depending on a checking result and therebytemporarily storing the second write data TRAN_WDATA2.

Each of the first to third nonvolatile memory devices C40, C50 and C60may retain stored data even though power is not supplied. In particular,each of the first to third nonvolatile memory devices C40, C50 and C60may store write data WDATA provided from the host C10, through a writeoperation, and may provide read data (not shown) stored therein, to thehost C10, through a read operation.

While each of the first to third nonvolatile memory devices C40, C50 andC60 may be realized by a nonvolatile memory such as a flash memory, forexample, a NAND flash memory, it is to be noted that each of the firstto third nonvolatile memory devices C40, C50 and C60 may be realized byany one memory among memories such as a phase change memory (PCRAM:phase change random access memory), a resistive memory (RRAM (ReRAM):resistive random access memory), a ferroelectric memory (FRAM:ferroelectric random access memory) and a spin transfer torque magneticmemory (STT-RAM (STT-MRAM): spin transfer torque magnetic random accessmemory).

Each of the first to third nonvolatile memory devices C40, C50 and C60includes the plurality of memory blocks MEMORY BLOCK<0, 1, 2, . . . >.In other words, each of the first to third nonvolatile memory devicesC40, C50 and C60 may store write data WDATA provided from the host C10,in the memory blocks MEMORY BLOCK<0, 1, 2, . . . >, through a writeoperation, and may provide read data (not shown) stored in the memoryblocks MEMORY BLOCK<0, 1, 2, . . . >, to the host C10, through a readoperation.

Each of the memory blocks MEMORY BLOCK<0, 1, 2, . . . > included in eachof the first to third nonvolatile memory devices C40, C50 and C60includes a plurality of pages P<0, 1, 2, 3, 4, . . . . >. Also, whilenot shown in detail in the drawing, a plurality of memory cells areincluded in each of the pages P<0, 1, 2, 3, 4, . . . >.

Each of the memory blocks MEMORY BLOCK<0, 1, 2, . . . > included in eachof the first to third nonvolatile memory devices C40, C50 and C60 may beclassified as a single level cell (SLC) memory block or a multi-levelcell (MLC) memory block, depending on the number of bits which may bestored or expressed in one memory cell included therein. An SLC memoryblock includes a plurality of pages which are realized by memory cellseach storing 1 bit, and has excellent data computation performance andhigh durability. An MLC memory block includes a plurality of pages whichare realized by memory cells each storing multi-bit data (for example, 2or more bits), and may be more highly integrated than the SLC memoryblock since it has a larger data storage space than the SLC memoryblock.

In particular, the MLC memory block may be classified as an MLC memoryblock including a plurality of pages which are realized by memory cellseach capable of storing 2-bit data, a triple level cell (TLC) memoryblock including a plurality of pages which are realized by memory cellseach capable of storing 3-bit data, a quadruple level cell (QLC) memoryblock including a plurality of pages which are realized by memory cellseach capable of storing 4-bit data or a multiple level cell memory blockincluding a plurality of pages which are realized by memory cells eachcapable of storing 5 or more-bit data.

FIGS. 8A to 8E and 9A to 9D are diagrams to assist in the explanation ofthe operation of the memory system in accordance with the secondembodiment of the present disclosure.

First, a scheme in which the controller C30 described above withreference to FIGS. 6 and 7 classifies the write data WDATA inputted fromthe host C10, into the normal write data NMAL_WDATA, the first writedata TRAN_WDATA1 and the second write data TRAN_WDATA2, will bedescribed below by referring to several reference symbols which are usedin FIGS. 8A to 8E.

In detail, when the write data WDATA are inputted to the memory systemC20 from the host C10, write commands (not shown) respectivelycorresponding to the write data WDATA are inputted together, andtransaction information (not shown) of the write data WDATA are includedin the write commands, respectively.

In the transaction information of each of the write data WDATA, atransaction ID (identification) information TRID, a transaction commitinformation (not shown) and a transaction abort information (not shown)may be included.

Therefore, the controller C30 included in the memory system C20 maycheck transaction ID information TRID in the transaction informationincluded in the write commands, and thereby, may classify the write dataWDATA into the normal write data NMAL_WDATA which are not grouped into atransaction or the transaction write data TRAN_WDATA1 or TRAN_WDATA2which are grouped into a transaction.

For example, the controller C30 may classify write data WDATA of whichtransaction ID information TRID have the value of 1, among the writedata WDATA inputted from the host C10, into the first write dataTRAN_WDATA1.

Similarly, the controller C30 may classify write data WDATA of whichtransaction ID information TRID have the value of 2, among the writedata WDATA inputted from the host C10, into the second write dataTRAN_WDATA2.

Also, the controller C30 may classify write data WDATA of whichtransaction ID information TRID are not set to any value, among thewrite data WDATA inputted from the host C10, into the normal write dataNMAL_WDATA.

For reference, the fact that transaction ID information TRID are not setto any value may mean a case where they are set to a predefined initialvalue or a value that is meaningless as a transaction ID information.

In a write command corresponding to start data of the write dataTRAN_WDATA1 or TRAN_WDATA2 which are grouped into a transaction, thereis additionally included the total size information TTSIZE1 or TTSIZE2on a total size of the write data TRAN_WDATA1 or TRAN_WDATA2.

For example, in a first write command corresponding to start data of thefirst write data TRAN_WDATA1 which are grouped into the firsttransaction, there is additionally included the first total sizeinformation TTSIZE1 on a total size of the first write data TRAN_WDATA1.

Because of this fact, the controller C30 may check the first total sizeinformation TTSIZE1 by checking the first write command before the startdata to be inputted first among the first write data TRAN_WDATA1 isinputted from the host C10.

That is, the controller C30 may check the first determined size of thefirst write data TRAN_WDATA1, by checking the first total sizeinformation TTSIZE1 before the first write data TRAN_WDATA1 are inputtedfrom the host C10.

Similarly, in a second write command corresponding to start data of thesecond write data TRAN_WDATA2 which are grouped into the secondtransaction, there is additionally included the second total sizeinformation TTSIZE2 on a total size of the second write dataTRAN_WDATA2.

Because of this fact, the controller C30 may check the second total sizeinformation TTSIZE2 by checking the second write command before thestart data to be inputted first among the second write data TRAN_WDATA2is inputted from the host C10.

That is, the controller C30 may check the second determined size of thesecond write data TRAN_WDATA2, by checking the second total sizeinformation TTSIZE2 before the second write data TRAN_WDATA2 areinputted from the host C10.

The controller C30 allocates the plurality of write buffers C31, C32,C33 and C34 in the volatile memory 144 before the write data WDATA areinputted from the host C10. In this way, each of the plurality of writebuffers C31, C32, C33 and C34 is fixed to the predefined size. Forexample, as exemplarily illustrated in FIGS. 8A to 8E, the predefinedsize may be set to 6. That is, each of the plurality of write buffersC31, C32, C33 and C34 may store six pieces of the write data.

In this way, after the plurality of write buffers C31, C32, C33 and C34are allocated in advance in the volatile memory 144, when the normalwrite data NMAL_WDATA which are not grouped into a transaction areinputted from the host C10, the controller C30 stores the normal writedata NMAL_WDATA by distributing them over write buffers which are notset for exclusive use for a transaction, among the plurality of writebuffers C31, C32, C33 and C34.

After the plurality of write buffers C31, C32, C33 and C34 are allocatedin advance in the volatile memory 144, when the first write dataTRAN_WDATA1 which are grouped into the first transaction and the firsttotal size information TTSIZE1 on a total size of the first transactionare inputted from the host C10, the controller C30 sets, in response tothe first total size information TTSIZE1, the first exclusive use optionfor exclusively using at least one first write buffer among theplurality of write buffers C31, C32, C33 and C34, for the firsttransaction.

Also, after the plurality of write buffers C31, C32, C33 and C34 areallocated in advance in the volatile memory 144, when the second writedata TRAN_WDATA2 which are grouped into the second transaction and thesecond total size information TTSIZE2 on a total size of the secondtransaction are inputted from the host C10, the controller C30 sets, inresponse to the second total size information TTSIZE2, a secondexclusive use option for exclusively using at least one second writebuffer among the remaining write buffers except the first write bufferamong the plurality of write buffers C31, C32, C33 and C34, for thesecond transaction.

The controller C30 stores the normal write data NMAL_WDATA byappropriately distributing them over write buffers which are not set forexclusive use for a transaction, among the plurality of write buffersC31, C32, C33 and C34. In other words, a write buffer to be exclusivelyused for storing the normal write data NMAL_WDATA does not separatelyexist. Therefore, a time at which the normal write data NMAL_WDATAstored by being distributed over the plurality of write buffers C31,C32, C33 and C34 are stored in the nonvolatile memory devices C40, C50and C60 may not be defined in advance.

In the case of the first write buffer which is set for exclusive use forthe first transaction, it has a storage space equal to or larger thanthe first determined size corresponding to the first total sizeinformation TTSIZE1. The controller C30 may be aware of that, sincewhether the commit of the first transaction is completed is determinedat a time when the first write data TRAN_WDATA1 are stored in the firstwrite buffer by an amount corresponding to the first determined size,the first write data TRAN_WDATA1 are not inputted any more. Thus, thecontroller C30 checks whether the commit of the first transaction iscompleted, at a time when the first write data TRAN_WDATA1 are stored inthe first write buffer by an amount corresponding to the firstdetermined size. As a result of the checking, in the case where thecommit of the first write data TRAN_WDATA1 stored in the first writebuffer is completed, the controller C30 performs a first flush operationfor the first write buffer, and thereby, performs a first writeoperation of storing the first write data TRAN_WDATA1 stored in thefirst write buffer, in the nonvolatile memory devices C40, C50 and C60.After performing the first write operation, the controller C30 resetsthe first exclusive use option for the first write buffer. The fact thatthe first exclusive use option for the first write buffer is reset meansthat the first write buffer is not used any more for exclusive use forthe first transaction.

The controller C30 checks whether the first write data TRAN_WDATA1 areaborted or not, at each determined time, even before the first writedata TRAN_WDATA1 are stored by the first determined size in the firstwrite buffer. As a result of the checking, in the case where the firstwrite data TRAN_WDATA1 stored in the first write buffer are aborted, thecontroller C30 discards the first write data TRAN_WDATA1 stored in thefirst write buffer, and resets the first exclusive use option for thefirst write buffer. The determined time at which whether the first writedata TRAN_WDATA1 are aborted is checked may be a time at which each ofthe first write data TRAN_WDATA1 is inputted to the first write buffer.

In the case of the second write buffer which is set for exclusive usefor the second transaction, it has a storage space equal to or largerthan the second determined size corresponding to the second total sizeinformation TTSIZE2. The controller C30 may be aware of that, sincewhether the commit of the second transaction is completed is determinedat a time when the second write data TRAN_WDATA2 are stored in thesecond write buffer by an amount corresponding to the second determinedsize, the second write data TRAN_WDATA2 are not inputted any more. Thus,the controller C30 checks whether the commit of the second transactionis completed, at a time when the second write data TRAN WDATA2 arestored in the second write buffer by an amount corresponding to thesecond determined size. As a result of the checking, in the case wherethe commit of the second write data TRAN_WDATA2 stored in the secondwrite buffer is completed, the controller C30 performs a second flushoperation for the second write buffer, and thereby, performs a secondwrite operation of storing the second write data TRAN_WDATA2 stored inthe second write buffer, in the nonvolatile memory devices C40, C50 andC60. After performing the second write operation, the controller C30resets the second exclusive use option for the second write buffer. Thefact that the second exclusive use option for the second write buffer isreset means that the second write buffer is not used any more forexclusive use for the second transaction.

The controller C30 checks whether the second write data TRAN_WDATA2 areaborted or not, at each determined time, even before the second writedata TRAN_WDATA2 are stored by the second determined size in the secondwrite buffer. As a result of the checking, in the case where the secondwrite data TRAN_WDATA2 stored in the second write buffer are aborted,the controller C30 discards the second write data TRAN_WDATA2 stored inthe second write buffer, and resets the second exclusive use option forthe second write buffer. The determined time at which whether the secondwrite data TRAN_WDATA2 are aborted is checked may be a time at whicheach of the second write data TRAN_WDATA2 is inputted to the secondwrite buffer.

In the case where a time at which the commit of the first transaction ischecked and a time at which the commit of the second transaction ischecked are within a set first time interval, the controller C30synchronizes a time at which the first flush operation is performed forthe first write buffer in correspondence to the commit of the firsttransaction and a time at which the second flush operation is performedfor the second write buffer in correspondence to the commit of thesecond transaction.

In the case where a performance time of the first flush operation and aperformance time of the second flush operation are synchronized, it maybe regarded that a time at which the performance of the first writeoperation of storing the first write data TRAN_WDATA1 stored in thefirst write buffer in the nonvolatile memory devices C40, C50 and C60 isstarted and a time at which the performance of the second writeoperation of storing the second write data TRAN_WDATA2 stored in thesecond write buffer in the nonvolatile memory devices C40, C50 and C60is started are synchronized. Hence, there is a high possibility that atime at which the performance of the first write operation is completedand a time at which the performance of the second write operation iscompleted do not have a large difference.

Thus, in the case where a performance time of the first flush operationand a performance time of the second flush operation are synchronized,the controller C30 may synchronize a time at which a firstacknowledgement signal for notifying the host C10 that the performanceof the first write operation linked to the first flush operation iscompleted is transferred to the host C10 and a time at which a secondacknowledgement signal for notifying the host C10 that the performanceof the second write operation linked to the second flush operation iscompleted is transferred to the host C10.

Of course, even in the case where a performance time of the first flushoperation and a performance time of the second flush operation aresynchronized, there may be a case where a time at which the performanceof the first write operation is completed and a time at which theperformance of the second write operation is completed have a largedifference.

Thus, even in the case where a performance time of the first flushoperation and a performance time of the second flush operation aresynchronized, the controller C30 may synchronize, only in the case wherea time at which a first acknowledgement signal for notifying the hostC10 that the performance of the first write operation linked to thefirst flush operation is completed is generated and a time at which asecond acknowledgement signal for notifying the host C10 that theperformance of the second write operation linked to the second flushoperation is completed is generated are within a set second timeinterval, a time at which the first acknowledgement signal istransferred to the host C10 and a time at which the secondacknowledgement signal is transferred to the host C10.

In summary, the controller C30 may perform a first synchronizationoperation of synchronizing a time at which the first acknowledgementsignal is transferred to the host C10 and a time at which the secondacknowledgement signal is transferred to the host C10, by checking onlywhether a performance time of the first flush operation and aperformance time of the second flush operation are synchronized

Also, the controller C30 may perform a second synchronization operationof synchronizing a time at which the first acknowledgement signal istransferred to the host C10 and a time at which the secondacknowledgement signal is transferred to the host C10, only in the casewhere a time at which the first acknowledgement signal is generated anda time at which the second acknowledgement signal is generated arewithin the set second time interval, even in the case where aperformance time of the first flush operation and a performance time ofthe second flush operation are synchronized.

For reference, the first synchronization operation and the secondsynchronization operation are operations that cannot be performedsimultaneously. Therefore, in the case where the controller C30 performsthe first synchronization operation, the second synchronizationoperation is not performed. Conversely, in the case where the controllerC30 performs the second synchronization operation, the firstsynchronization operation is not performed. Whether the controller C30will perform the first synchronization operation or the secondsynchronization operation may be defined in advance depending on memorycharacteristics and a designer's choice.

The set first time interval serving as a reference for determiningwhether to synchronize a performance time of the first flush operationand a performance time of the second flush operation may be defined inadvance depending on the characteristics of a memory system and adesigner's choice.

Similarly, the set second time interval serving as a reference fordetermining whether to synchronize a time at which the firstacknowledgement signal is transferred to the host C10 and a time atwhich the second acknowledgement signal is transferred to the host C10may be defined in advance depending on the characteristics of a memorysystem and a designer's choice.

Referring to FIG. 8A, it may be assumed that it is a state in which thecontroller C30 has allocated the four write buffers C31, C32, C33 andC34 each capable of storing six pieces of the write data WDATA, in thevolatile memory 144, before a first time.

In succession, it may be assumed that total four pieces of the writedata WDATA are inputted from the host C10 at the first time. Thecontroller C30 may check the transaction ID information TRIG of therespective four pieces of the write data WDATA inputted from the hostC10, and may classify all the four pieces of the write data WDATA intothe normal write data NMAL_WDATA which are not grouped into atransaction.

Then, the controller C30 checks whether there is a write buffer which isset for exclusive use for a transaction, among the four write buffersC31, C32, C33 and C34 allocated in the volatile memory 144 at the firsttime. As a result of the checking, it is a state in which none of thefour write buffers C31, C32, C33 and C34 allocated in the volatilememory 144 at he first time are set for exclusive use for a transaction.

Therefore, the controller C30 may store A, B, C and D as four pieces ofthe normal write data NMAL_WDATA inputted from the host C10 at the firsttime, by appropriately distributing them over the four write buffersC31, C32, C33 and C34. For example, in the figure, A and B as twopreceding data among A, B, C and D as the four pieces of the normalwrite data NMAL_WDATA inputted from the host C1.0 at the first time arestored in the first write buffer C31. Then, C and D as subsequent twopieces of the write data among A, B, C and D as the four pieces of thenormal write data NMAL_WDATA inputted from the host C10 at the firsttime are stored in the second write buffer C32.

In summary, the controller C30 distributedly stores A, B, C and D asfour pieces of the normal write data NMAL_WDATA inputted from the hostC10 at the first time, two by two in the first write buffer C31 and thesecond write buffer C32 among the four write buffers C31, C32, C33 andC34. As a result, in each of the first write buffer C31 and the secondwrite buffer C32 each having a storage space capable of storing sixpieces of the write data, two pieces of the normal write data NMAL_WDATAare stored and empty space available for four other pieces of the writedata.

Referring to FIG. 86, it may be assumed that, at a second timesuccessive to the first time shown in FIG. 8A, total five pieces of thewrite data WDATA are inputted from the host C10. A sequence in which thefive pieces of the write data WDATA are inputted from the host C10 isnot defined in advance, and it may be assumed that they are inputtedrandomly.

In detail, the controller C30 checks the transaction ID information TRIDof the respective five pieces of the write data WDATA inputted from thehost C10 at the second time, and classifies the five pieces of the writedata WDATA into three pieces of the first write data TRAN_WDATA1 and twopieces of the normal write data NMAL_WDATA.

In further detail, the controller C30 determines that, among the fivepieces of the write data WDATA inputted from the host C10 at the secondtime, 0, 1 and 2 as three pieces of the write data WDATA of whichtransaction ID information TRID have the value of 1 are write data WDATAwhich are grouped into the first transaction, and classifies them intothe first write data TRAN_WDATA1.

In a first write command (not shown) corresponding to 0 as start dataamong 0, 1 and 2 grouped into the first write data TRAN_WDATA1, thefirst total size information TTSIZE1 is included. Thus, the controllerC30 may check from the first write command corresponding to 0 that thefirst total size information TTSIZE1 is 5.

In this way, after checking that the first total size informationTTSIZE1 is 5, the controller C30 checks whether there is a write bufferhaving an empty space capable of storing a total of five pieces of thefirst write data TRAN_WDATA1 which are grouped into the firsttransaction, among the four write buffers C31, C32, C33 and C34allocated in the volatile memory 144.

As a result of the checking, because two pieces of the normal write dataNMAL_WDATA have been stored in each of the first write buffer C31 andthe second write buffer C32 among the four write buffers C31, C32, C33and C34 at the first time described above, each of the first writebuffer C31 and the second write buffer C32 has an empty space availablefor four other pieces of the write data. Therefore, each of the firstwrite buffer C31 and the second write buffer C32 is not suitable foraccommodating a total of five pieces of the first write data TRAN_WDATA1which are grouped into the first transaction.

On the other hand, because no write data has been stored in each of thethird write buffer C33 and the fourth write buffer C34 among the fourwrite buffers C31, C32, C33 and C34 at the first time described above,each of the third write buffer C33 and the fourth write buffer C34 hasan empty space available for six other pieces of the write data.Therefore, each of the third write buffer C33 and the fourth writebuffer C34 is suitable for accommodating a total of five pieces of thefirst write data TRAN_WDATA1 which are grouped into the firsttransaction.

In other words, an empty space capable of accommodating the firstdetermined size exists in each of one or more write buffers C33 and C34among the four write buffers C31, C32, C33 and C34.

Because no write data has been stored in each of the third write bufferC33 and the fourth write buffer C34 among the four write buffers C31,C32, C33 and C34 at the first time described above, the third writebuffer C33 and the fourth write buffer C34 are, in the same manner, in astate in which each of them has an empty space available for six piecesof the write data, at the second time.

Thus, it is possible to set the first exclusive use option for any onewrite buffer of the third write buffer C33 and the fourth write bufferC34 among the four write buffers C31, C32, C33 and C34 and manage thecorresponding write buffer as the first write buffer. For reference, itis illustrated in FIG. 8B that the first exclusive use option is set forthe third write buffer C33 and thus the third write buffer C33 isexclusively used for the first transaction.

In this way, the controller C30 may check the first total sizeinformation TTSIZE1 before 0 as the start data among 0, 1 and 2 groupedinto the first write data TRAN_WDATA1 is inputted, and thereby, may setthe third write buffer C33 among the four write buffers C31, C32, C33and C34 allocated in advance in the volatile memory 144, as the firstwrite buffer for exclusive use for the first transaction.

After all the five pieces of the write data WDATA are inputted from thehost C10 at the second time, the controller C30 may check that only 0, 1and 2 exist as the first write data TRAN_WDATA1 which are grouped intothe first transaction. In other words, the controller C30 may checkthat, at a time when the five pieces of the write data WDATA areinputted from the host C10 at the second time, the first transaction isnot completely committed yet (Transaction Uncomplete).

In summary, the controller C30 selects the third write buffer C33 havingspace capable of storing a total of six pieces of the write data as thefirst write buffer for exclusive use for the first transaction at thesecond time, stores 0, 1 and 2 as the three pieces of the first writedata TRAN_WDATA1 inputted from the host C10, in the third write bufferC33, and keeps space available for three remaining pieces of the writedata.

Moreover, the controller C30 determines that, among the five pieces ofthe write data WDATA inputted from the host C10 at the second time, Eand F as write data WDATA of which transaction ID information TRID arenot set to any value are write data WDATA which are not grouped into atransaction, and classifies them into the normal write data NMAL_WDATA.

In succession, the controller C30 checks whether there is a write bufferwhich is set for exclusive use for a transaction, among the four writebuffers C31, C32, C33 and C34 allocated in the volatile memory 144, atthe second time. As a result of the checking, it is a state in which thethird write buffer C33 is set for exclusive use for the firsttransaction at the second time. For reference, in order for the thirdwrite buffer C33 to be set as the first write buffer for exclusive usefor the first transaction at the second time, at least one piece of thefirst write data TRAN_WDATA1 should be inputted. Therefore, it isassumed that FIG. 8B represents a case where at least one piece of thefirst write data TRAN_WDATA1 is inputted earlier than the normal writedata NMAL_WDATA.

Thus, the controller C30 may store E and F as the two pieces of thenormal write data NMAL_WDATA inputted from the host C10 at the secondtime, by appropriately distributing them over the remaining writebuffers C31, C32 and C34 except the third write buffer C33 set forexclusive use for the first transaction among the four write buffersC31, C32, C33 and C34. For example, in the figure, E and F as the twopieces of the normal write data NMAL_WDATA inputted from the host C10 atthe second time are stored in the first write buffer C31.

In summary, the controller C30 stores E and F as the two pieces of thenormal write data NMAL_WDATA inputted from the host C10 at the secondtime, in the first write buffer C31 among the four write buffers C31,C32, C33 and C34. As a result, in the first write buffer C31 having thestorage space capable of storing six pieces of the write data, a totalof four pieces of the normal write data NMAL_WDATA are stored as twopieces of the write data are stored at each of the first time and thesecond time, and a space remains available for two other pieces of thewrite data.

Referring to FIG. 8C, it may be assumed that, at a third time successiveto the second time shown in FIG. 8B, total eight pieces of the writedata WDATA are inputted from the host C10. A sequence in which the eightpieces of the write data WDATA are inputted from the host C10 is notdefined in advance, and it may be assumed that they are inputtedrandomly.

In detail, the controller C30 checks the transaction ID information TRIDof the respective eight pieces of the write data WDATA inputted from thehost C10 at the third time, and classifies the eight pieces of the writedata WDATA into two pieces of the first write data TRAN_WDATA1, fourpieces of the second write data TRAN_WDATA2 and two pieces of the normalwrite data NMAL_WDATA.

In further detail, the controller C30 determines that, among the eightpieces of the write data WDATA inputted from the host C10 at the thirdtime, 3 and 4 as two pieces of the write data WDATA of which transactionID information TRID have the value of 1 are write data WDATA which aregrouped into the first transaction, and classifies them into the firstwrite data TRAN_WDATA1.

At this time, it is a state in which, through the operation at thesecond time described above with reference to FIG. 8B, the third writebuffer C33 among the four write buffers C31, C32, C33 and C34 allocatedin the volatile memory 144 has already been set for exclusive use forthe first transaction and is being used as the first write buffer forstoring the first write data TRAN_WDATA1.

Therefore, the controller C30 immediately stores 3 and 4 grouped intothe first write data TRAN_WDATA1 in the first write buffer at the thirdtime without a separate additional operation. At this time, it is astate in which, through the operation at the second time described abovewith reference to FIG. 8B, the controller C30 has set the third writebuffer C33 capable of storing a total of six pieces of the write data,as the first write buffer for exclusive use for the first transaction,has stored only 0, 1 and 2 as three pieces of the write data, and haskept a space available for three other pieces of the write data.

Because of this fact, the controller C30 immediately stores 3 and 4grouped into the first write data TRAN_WDATA1 in the first write bufferat the third time without a separate additional operation. In this way,as 3 and 4 grouped into the first write data TRAN_WDATA1 are stored inthe first write buffer at the third time, it becomes a state in whichthe first write data TRAN_WDATA1 are stored in a space capable ofstoring five pieces of the write data in a space available for storingsix pieces of the write data in the first write buffer.

At a time when 0, 1, 2, 3 and 4 as the first write data TRAN_WDATA1grouped into the first transaction are stored in the first write bufferand thus the first write data TRAN_WDATA1 are stored in the spacecapable of storing five pieces of the write data in space available forstoring six pieces of the write data in the first write buffer, thecontroller C30 may check that it is a state in which the commit of thefirst transaction is completed (Transaction Complete).

In summary, by additionally storing 3 and 4 as the two pieces of thefirst write data TRAN_WDATA1 inputted from the host C10 at the thirdtime, in the third write buffer C33 which is set as the first writebuffer for exclusive use for the first transaction at the second timedescribed above, the controller C30 may check that it is a state inwhich the commit of the first transaction is completed (TransactionComplete).

Further, the controller C30 determines that, among the eight pieces ofthe write data WDATA inputted from the host C10 at the third time, 110,111, 112 and 113 as four pieces of the write data WDATA of whichtransaction ID information TRID have the value of 2 are write data WDATAwhich are grouped into the second transaction, and classifies them intothe second write data TRAN_WDATA2.

In a second write command (not shown) corresponding to 110 as start dataamong 110, 111, 112 and 113 grouped into the second write dataTRAN_WDATA2, the second total size information TTSIZE2 is included.Thus, the controller C30 may check from the second write commandcorresponding to 110 that the second total size information TTSIZE2 is4.

In this way, after checking that the second total size informationTTSIZE2 is 4, the controller C30 checks whether there is a write bufferhaving an empty space capable of storing a total of four pieces of thesecond write data TRAN_WDATA2 which are grouped into the secondtransaction, among the remaining write buffers C31, C32 and C34 exceptthe first write buffer set for exclusive use for the first transactionallocated in the volatile memory 144.

As a result of the checking, it is a state in which the third writebuffer C33 among the four write buffers C31, C32, C33 and C34 has beenset as the first write buffer for exclusive use for the firsttransaction at the second time described above.

Therefore, whether there is a write buffer having an empty space capableof storing a total of four pieces of the second write data TRAN_WDATA2which are grouped into the second transaction, among the remaining threewrite buffers C31, C32 and C34 except the third write buffer C33 ischecked.

As a result of the checking, because a total of four pieces of thenormal write data NMAL_WDATA have been stored in the first write bufferC31 among the three write buffers C31, C32 and C34 as two pieces of thenormal write data NMAL_WDATA are stored at each of the first time andthe second time described above, it is a state in which the first writebuffer C31 has an empty space capable of storing two other pieces of thewrite data. Therefore, the first write buffer C31 is not suitable foraccommodating the total four pieces of the second write data TRAN_WDATA2which are grouped into the second transaction.

Because the two pieces of the normal write data NMAL_WDATA have beenstored in the second write buffer C32 among the three write buffers C31,C32 and C34 at the first time described above, it is a state in whichthe second write buffer C32 has an empty space capable of storing fourpieces of the write data. Therefore, the second write buffer C32 issuitable for accommodating a total of four pieces of the second writedata TRAN_WDATA2 which are grouped into the second transaction.

Because no write data has been stored in the fourth write buffer C34among the three write buffers C31, C32 and C34 at the first time and thesecond time described above, it is a state in which the fourth writebuffer C34 has space available for storing six pieces of the write data.Therefore, the fourth write buffer C34 is suitable for accommodating thetotal four pieces of the second write data TRAN_WDATA2 which are groupedinto the second transaction.

In other words, an empty space capable of accommodating the seconddetermined size exists in each of one or more write buffers C32 and C34among the three write buffers C31, C32 and C34.

In this way, because each of one or more write buffers C32 and C34 hasan empty space capable of accommodating the second determined size, thecontroller C30 sets the second exclusive use option for a write bufferof which size of an empty space is relatively smaller, and manages thecorresponding write buffer as the second write buffer. That is, thecontroller C30 sets the second exclusive use option for the second writebuffer C32 of which size of an empty space is relatively smaller betweenthe second write buffer C32 and the fourth write buffer C34 each havingan empty space equal to or larger than the second determined size, andmanages the second write buffer C32 as the second write buffer.

In this way, the controller C30 may check the second total sizeinformation TTSIZE2 before 110 as the start data among 110, 111, 112 and113 grouped into the second write data TRAN_WDATA2 is inputted, andthereby, may set the second write buffer C32 among the four writebuffers C31, C32, C32 and C34 allocated in advance in the volatilememory 144, as the second write buffer for exclusive use for the secondtransaction.

Thus, each time each of the four pieces of the second write dataTRAN_WDATA2 grouped into the second transaction among the eight piecesof the write data WDATA inputted from the host C10 is inputted at thethird time, the controller C30 stores each of the four pieces of thesecond write data TRAN_WDATA2 in the second write buffer which is setfor exclusive use for the second transaction.

In this way, as 110, 111, 112 and 113 grouped into the second write dataTRAN_WDATA2 are stored in the second write buffer at the third time, itbecomes a state in which the second write data TRAN_WDATA2 are stored inthe entire empty space available for four pieces of the write data whichis included in the second write buffer.

At a time when 110, 111, 112 and 113 as the second write dataTRAN_WDATA2 grouped into the second transaction are stored in the secondwrite buffer and thus the second write data TRAN_WDATA2 are stored inthe entire empty space for available for four pieces of the write datawhich is included in the second write buffer, the controller C30 maycheck that it is a state in which the commit of the second transactionis completed (Transaction Complete).

In summary, by selecting the second write buffer C32 having the spacefor a total of four pieces of the write data as the second write bufferfor exclusive use for the second transaction at the third time andstoring 110, 111, 112 and 113 as the four pieces of the second writedata TRAN_WDATA2 inputted from the host C10, the controller C30 maycheck that it is a state in which the commit of the second transactionis completed (Transaction Complete).

Moreover, the controller C30 determines that, among the eight pieces ofthe write data WDATA inputted from the host C10 at the third time, G andH as write data WDATA of which transaction ID information TRID are notset to any value are write data WDATA which are not grouped into atransaction, and classifies them into the normal write data NMAL_WDATA.

In succession, the controller C30 checks whether there is a write bufferwhich is set for exclusive use for a transaction, among the four writebuffers C31, C32, C33 and C34 allocated in the volatile memory 144, atthe third time. As a result of the checking, it is a state in which thethird write buffer C33 is set for exclusive use for the firsttransaction and the second write buffer C32 is set for exclusive use forthe second transaction at the third time. For reference, in order forthe second write buffer C32 to be set as the second write buffer forexclusive use for the second transaction at the third time, at least onepiece of the second write data TRAN_WDATA2 should be inputted.Therefore, it is assumed that FIG. 8C represents a case where at leastone piece of the second write data TRAN_WDATA2 is inputted earlier thanthe normal write data NMAL_WDATA.

Thus, the controller C30 may store G and H as the two pieces of thenormal write data NMAL_WDATA inputted from the host C10 at the thirdtime, by appropriately distributing them over the remaining writebuffers C31 and C34 except the third write buffer C33 set for exclusiveuse for the first transaction and the second write buffer C32 set forexclusive use for the second transaction among the four write buffersC31, C32, C33 and C34. For example, in the figure, G and H as the twopieces of the normal write data NMAL_WDATA inputted from the host C10 atthe third time are stored in the fourth write buffer C34.

In summary, the controller C30 stores G and H as the two pieces of thenormal write data NMAL_WDATA inputted from the host C10 at the thirdtime, in the fourth write buffer C34 among the four write buffers C31,C32, C33 and C34. As a result, in the fourth write buffer C34 having thestorage space for six pieces of the write data, the two pieces of thenormal write data NMAL_WDATA are stored at the third time, and a spacefor four pieces of the write data is kept empty.

In the state as shown in FIG. 8C, since both the first transaction andthe second transaction are commit-completed, it is a case in which thefirst write buffer and the second write buffer should be flushed.

Since it is assumed that an input sequence of the write data WDATAinputted from the host C10 at the third time is random, a time at whichthe commit of the first transaction is completed may precede a time atwhich the commit of the second transaction is completed, or a time atwhich the commit of the second transaction is completed may precede atime at which the commit of the first transaction is completed.

In the case where a time at which the commit of the first transaction iscompleted precedes a time at which the commit of the second transactionis completed, it may be assumed that the commit of the secondtransaction is completed within the set first time interval from thetime at which the commit of the first transaction is completed.

Conversely, in the case where a time at which the commit of the secondtransaction is completed precedes a time at which the commit of thefirst transaction is completed, it may be assumed that the commit of thefirst transaction is completed within the set first time interval fromthe time at which the commit of the second transaction is completed.

In this way, in the case where difference between a time at which thecommit of the first transaction is completed and a time at which thecommit of the second transaction is completed are within the set firsttime interval, the controller C30 synchronizes a time at which a firstflush operation FLUSH1 is performed for the first write buffer incorrespondence to the commit of the first transaction and a time atwhich a second flush operation FLUSH2 is performed for the second writebuffer in correspondence to the commit of the second transaction.

In this way, by synchronizing a performance time of the first flushoperation FLUSH1 and a performance time of the second flush operationFLUSH2, it may be regarded that a time at which the performance of afirst write operation WRITE1 of storing the first write data TRAN_WDATA1stored in the first write buffer in the nonvolatile memory devices C40,C50 and C60 is started and a time at which the performance of a secondwrite operation WRITE2 of storing the second write data TRAN_WDATA2stored in the second write buffer in the nonvolatile memory devices C40,C50 and C60 is started are synchronized.

Accordingly, as in the case of a first synchronization operation shownin FIG. 9A, the controller C30 may synchronize, when a performance timeof the first flush operation FLUSH1 and a performance time of the secondflush operation FLUSH2 are synchronized, a time at which a firstacknowledgement signal ACK1 for notifying the host C10 that theperformance of the first write operation WRITE1 linked to the firstflush operation FLUSH1 is completed is transferred to the host C10 and atime at which a second acknowledgement signal ACK2 for notifying thehost C10 that the performance of the second write operation WRITE2linked to the second flush operation FLUSH2 is completed is transferredto the host C10.

Of course, as in the case of a first synchronization operation shown inFIG. 9B, the controller C30 may not synchronize, when a performance timeof the first flush operation FLUSH1 and a performance time of the secondflush operation FLUSH2 are not synchronized, a time at which a firstacknowledgement signal ACK1 for notifying the host C10 that theperformance of the first write operation WRITE1 linked to the firstflush operation FLUSH1 is completed is transferred to the host C10 and atime at which a second acknowledgement signal ACK2 for notifying thehost C10 that the performance of the second write operation WRITE2linked to the second flush operation FLUSH2 is completed is transferredto the host C10.

Also, as in the case of a second synchronization operation shown in FIG.9C, even in the case where a performance time of the first flushoperation FLUSH1 and a performance time of the second flush operationFLUSH2 are synchronized, only in the case where a time at which a firstacknowledgement signal ACK1 for notifying the host C10 that theperformance of the first write operation WRITE1 linked to the firstflush operation FLUSH1 is completed is generated and a time at which asecond acknowledgement signal ACK2 for notifying the host C10 that theperformance of the second write operation WRITE2 linked to the secondflush operation FLUSH2 is completed is generated are within the setsecond time interval, the controller C30 may synchronize a time at whichthe first acknowledgement signal ACK1 is transferred to the host C10 anda time at which the second acknowledgement signal ACK2 is transferred tothe host C10.

Of course, as in the case of a second synchronization operation shown inFIG. 9D, even in the case where a performance time of the first flushoperation FLUSH1 and a performance time of the second flush operationFLUSH2 are synchronized, in the case where a time at which a firstacknowledgement signal ACK1 for notifying the host C10 that theperformance of the first write operation WRITE1 linked to the firstflush operation FLUSH1 is completed is generated and a time at which asecond acknowledgement signal ACK2 for notifying the host C10 that theperformance of the second write operation WRTIE2 linked to the secondflush operation FLUSH2 is completed is generated are not within the setsecond time interval, the controller C30 may not synchronize a time atwhich the first acknowledgement signal ACK1 is transferred to the hostC10 and a time at which the second acknowledgement signal ACK2 istransferred to the host C10.

Referring again to FIG. 8C, after completing the performance of thefirst write operation WRITE1, the controller C30 resets the setting forthe first write buffer for exclusive use for the first transaction. Thatis, the controller C30 has used the third write buffer C33 as the firstwrite buffer for exclusive use for the first transaction, by setting thefirst exclusive use option for the third write buffer C33 among the fourwrite buffers C31, C32, C33 and C34 allocated in the volatile memory144, at the second time described above. Therefore, by resetting thefirst exclusive use option for the first write buffer after completingthe performance of the first write operation WRITE1 at the third time,the third write buffer C33 having been used as the first write buffermay not be used for exclusive use for the first transaction, like beforethe second time. Namely, the third write buffer C33 having beenexclusively used to store the first write data TRAN_WDATA1 at the secondtime and the third time may be used to store, for example, normal writedata NMAL_WDATA, after the third time.

Similarly, after completing the performance of the second writeoperation WRITE2, the controller C30 resets the setting for the secondwrite buffer for exclusive use for the second transaction. That is, thecontroller C30 has used the second write buffer C32 as the second writebuffer for exclusive use for the second transaction, by setting thesecond exclusive use option for the second write buffer C32 among thefour write buffers C31, C32, C33 and C34 allocated in the volatilememory 144, at the third time. Therefore, by resetting the secondexclusive use option for the second write buffer after completing theperformance of the second write operation WRITE2 at the third time, thesecond write buffer C32 having been used as the second write buffer maynot be used for exclusive use for the second transaction, like beforethe third time. Namely, the second write buffer C32 having beenexclusively used to store the second write data TRAN_WDATA2 at the thirdtime may be used to store, for example, normal write data NMAL_WDATA,after the third time.

Referring to FIG. 8D, it may be assumed that, at a third time successiveto the second time shown in FIG. 8B, total seven pieces of the writedata WDATA are inputted from the host C10. A sequence in which the sevenpieces of the write data WDATA are inputted from the host C10 is notdefined in advance, and it may be assumed that they are inputtedrandomly.

In detail, the controller C30 checks the transaction ID information TRIDof the respective seven pieces of the write data WDATA inputted from thehost C10 at the third time, and classifies the seven pieces of the writedata WDATA into one piece of the first write data TRAN_WDATA1, fourpieces of the second write data TRAN_WDATA2 and two pieces of the normalwrite data NMAL_WDATA.

In further detail, the controller C30 determines that, among the sevenpieces of the write data WDATA inputted from the host C10 at the thirdtime, 3 as one piece of the write data WDATA of which transaction IDinformation TRID has the value of 1 is write data WDATA which is groupedinto the first transaction, and classifies it into the first write dataTRAN_WDATA1.

At this time, it is a state in which, through the operation at thesecond time described above with reference to FIG. 8B, the third writebuffer C33 among the four write buffers C31, C32, C33 and C34 allocatedin the volatile memory 144 has already been set for exclusive use forthe first transaction and is being used as the first write buffer forstoring the first write data TRAN_WDATA1.

Therefore, the controller C30 immediately stores 3 grouped into thefirst write data TRAN_WDATA1 in the first write buffer at the third timewithout a separate additional operation. At this time, it is a state inwhich, through the operation at the second time described above withreference to FIG. 8B, the controller C30 has set the third write bufferC33 for total six pieces of the write data, as the first write bufferfor exclusive use for the first transaction, has stored only 0, 1 and 2as three pieces of the write data, and has kept a space for three piecesof the write data empty.

Because of this fact, the controller C30 immediately stores 3 groupedinto the first write data TRAN_WDATA1 in the first write buffer at thethird time without a separate additional operation. In this way, as 3grouped into the first write data TRAN_WDATA1 is stored in the firstwrite buffer at the third time, it becomes a state in which the firstwrite data TRAN_WDATA1 are stored in a space for four pieces of thewrite data in a total space capable of storing six pieces of the writedata which is included in the first write buffer.

After all the seven pieces of the write data WDATA are inputted from thehost C10 at the third time, the controller C30 may check that only 0, 1,2 and 3 exist as the first write data TRAN_WDATA1 which are grouped intothe first transaction. In other words, the controller C30 may checkthat, at a time when the seven pieces of the write data WDATA areinputted from the host C10, the first transaction is not completelycommitted yet (Transaction Uncomplete).

In summary, after additionally storing 3 as the one piece of the firstwrite data TRAN_WDATA1 inputted from the host C10 at the third time, inthe third write buffer C33 which is set as the first write buffer forexclusive use for the first transaction at the second time describedabove, the controller C30 keeps a space for two remaining pieces of thewrite data empty.

Further, the controller C30 determines that, among the seven pieces ofthe write data WDATA inputted from the host C10 at the third time, 110,111, 112 and 113 as four pieces of the write data WDATA of whichtransaction ID information TRID have the value of 2 are write data WDATAwhich are grouped into the second transaction, and classifies them intothe second write data TRAN_WDATA2.

In a second write command (not shown) corresponding to 110 as start dataamong 110, 111, 112 and 113 grouped into the second write dataTRAN_WDATA2, the second total size information TTSIZE2 is included.Thus, the controller C30 may check from the second write commandcorresponding to 110 that the second total size information TTSIZE2 is4.

In this way, after checking that the second total size informationTTSIZE2 is 4, the controller C30 checks whether there is a write bufferhaving an empty space capable of storing a total of four pieces of thesecond write data TRAN_WDATA2 which are grouped into the secondtransaction, among the remaining write buffers C31, C32 and C34 exceptthe first write buffer set for exclusive use for the first transactionamong the four write buffers C31, C32, C33 and C34 allocated in thevolatile memory 144.

As a result of the checking, it is a state in which the third writebuffer C33 among the four write buffers C31, C32, C33 and C34 has beenset as the first write buffer for exclusive use for the firsttransaction at the second time described above.

Therefore, whether there is a write buffer having an empty space capableof storing a total of four pieces of the second write data TRAN_WDATA2which are grouped into the second transaction, among the remaining threewrite buffers C31, C32 and C34 except the third write buffer C33 amongthe four write buffers C31, C32, C33 and C34, is checked.

As a result of the checking, because a total of four pieces of thenormal write data NMAL_WDATA have been stored in the first write bufferC31 among the three write buffers C31, C32 and C34 as two pieces of thenormal write data NMAL_WDATA are stored at each of the first time andthe second time described above, it is a state in which the first writebuffer C31 has an empty space available for two other pieces of thewrite data. Therefore, the first write buffer C31 is not suitable foraccommodating the total of four pieces of the second write dataTRAN_WDATA2 which are grouped into the second transaction.

Because the two pieces of the normal write data NMAL_WDATA have beenstored in the second write buffer C32 among the three write buffers C31,C32 and C34 at the first time described above, it is a state in whichthe second write buffer C32 has an empty space available for four piecesof the write data. Therefore, the second write buffer C32 is suitablefor accommodating the total of four pieces of the second write dataTRAN_WDATA2 which are grouped into the second transaction.

Because no write data has been stored in the fourth write buffer C34among the three write buffers C31, C32 and C34 at the first time and thesecond time described above, it is a state in which the fourth writebuffer C34 has an empty space available for six pieces of the writedata. Therefore, the fourth write buffer C34 is suitable foraccommodating the total of four pieces of the second write dataTRAN_WDATA2 which are grouped into the second transaction.

In other words, an empty space capable of accommodating the seconddetermined size exists in each of one or more write buffers C32 and C34among the three write buffers C31, C32 and C34.

In this way, because each of one or more write buffers C32 and C34 hasan empty space capable of accommodating the second determined size, thecontroller C30 sets the second exclusive use option for a write bufferof which size of an empty space is relatively smaller, and manages thecorresponding write buffer as the second write buffer. That is, thecontroller C30 sets the second exclusive use option for the second writebuffer C32 of which size of an empty space is relatively smaller betweenthe second write buffer C32 and the fourth write buffer C34 each havingan empty space equal to or larger than the second determined size, andmanages the second write buffer C32 as the second write buffer.

In this way, the controller C30 may check the second total sizeinformation TTSIZE2 before 110 as the start data among 110, 111, 112 and113 grouped into the second write data TRAN_WDATA2 is inputted, andthereby, may set the second write buffer C32 among the four writebuffers C31, C32, C32 and C34 allocated in advance in the volatilememory 144, as the second write buffer for exclusive use for the secondtransaction.

Thus, each time each of the four pieces of the second write dataTRAN_WDATA2 grouped into the second transaction among the seven piecesof the write data WDATA inputted from the host C10 is inputted at thethird time, the controller C30 stores each of the four pieces of thesecond write data TRAN_WDATA2 in the second write buffer which is setfor exclusive use for the second transaction.

In this way, as 110, 111, 112 and 113 grouped into the second write dataTRAN_WDATA2 are stored in the second write buffer at the third time, itbecomes a state in which the second write data TRAN_WDATA2 are stored inthe entire empty space capable of storing four pieces of the write datawhich is included in the second write buffer.

At a time when 110, 111, 112 and 113 as the second write dataTRAN_WDATA2 grouped into the second transaction are stored in the secondwrite buffer and thus the second write data TRAN_WDATA2 are stored inthe entire empty space capable of storing four pieces of the write datawhich is included in the second write buffer, the controller C30 maycheck that it is a state in which the commit of the second transactionis completed (Transaction Complete).

In summary, by selecting the second write buffer C32 having the spacecapable of storing a total of four pieces of the write data as thesecond write buffer for exclusive use for the second transaction at thethird time and storing 110, 111, 112 and 113 as the four pieces of thesecond write data TRAN_WDATA2 inputted from the host C10, the controllerC30 may check that it is a state in which the commit of the secondtransaction is completed (Transaction Complete).

Moreover, the controller C30 determines that, among the seven pieces ofthe write data WDATA inputted from the host C10 at the third time, G andH as write data WDATA of which transaction ID information TRID are notset to any value are write data WDATA which are not grouped into atransaction, and classifies them into the normal write data NMAL_WDATA.

In succession, the controller C30 checks whether there is a write bufferwhich is set for exclusive use for a transaction, among the four writebuffers C31, C32, C33 and C34 allocated in the volatile memory 144, atthe third time. As a result of the checking, it is a state in which thethird write buffer C33 is set for exclusive use for the firsttransaction and the second write buffer C32 is set for exclusive use forthe second transaction at the third time. For reference, in order forthe second write buffer C32 to be set as the second write buffer forexclusive use for the second transaction at the third time, at least onepiece of the second write data TRAN_WDATA2 should be inputted.Therefore, it is assumed that FIG. 3D represents a case where at leastone piece of the second write data TRAN_WDATA2 is inputted earlier thanthe normal write data NMAL_WDATA.

Thus, the controller C30 may store G and H as the two pieces of thenormal write data NMAL_WDATA inputted from the host C10 at the thirdtime, by appropriately distributing them over the remaining writebuffers C31 and C34 except the third write buffer C33 set for exclusiveuse for the first transaction and the second write buffer C32 set forexclusive use for the second transaction among the four write buffersC31, C32, C33 and C34. For example, in the figure, G and H as the twopieces of the normal write data NMAL_WDATA inputted from the host C10 atthe third time are stored in the fourth write buffer C34.

In summary, the controller C30 stores G and H as the two pieces of thenormal write data NMAL_WDATA inputted from the host C10 at the thirdtime, in the fourth write buffer C34 among the four write buffers C31,C32, C33 and C34. As a result, in the fourth write buffer C34 having thestorage space capable of storing six pieces of the write data, the twopieces of the normal write data NMAL_WDATA are stored at the third time,and a space available for four pieces of the write data is kept empty.

In the state as shown in FIG. 8D, since the first transaction iscommit-uncompleted and the second transaction is commit-completed, it isa case in which it is not necessary to perform a flush operation for thefirst write buffer and the second write buffer should be flushed.

When the state shown in FIG. 8B is changed to the state shown in FIG.8D, the first transaction maintains a state in which the commit thereofis not completed, and the second transaction is converted into a statein which the commit thereof is completed. Therefore, in the state asshown in FIG. 8D, it may not be seen that the commit of the firsttransaction is to be completed at which time, but it may be seen that atime at which the commit of the second transaction is completed precedesa time at which the commit of the first transaction is completed.Through this, it may be assumed that the commit of the first transactionis not completed within the set first time interval from the time atwhich the commit of the second transaction is completed.

In this way, in the case where a time at which the commit of the firsttransaction is completed and a time at which the commit of the secondtransaction is completed exceed the set first time interval, thecontroller C30 may not synchronize a time at which a first flushoperation FLUSH1 is performed for the first write buffer incorrespondence to the commit of the first transaction and a time atwhich a second flush operation FLUSH2 is performed for the second writebuffer in correspondence to the commit of the second transaction.

In other words, after the second flush operation FLUSH2 for the secondwrite buffer corresponding to the second transaction which iscommit-completed is performed, when the commit of the first transactionis completed at a certain time that is not within the set first timeinterval, the first flush operation FLUSH1 for the first write buffercorresponding to the first transaction may be performed.

In this way, by not synchronizing a performance time of the first flushoperation FLUSH1 and a performance time of the second flush operationFLUSH2, it may be regarded that a time at which the performance of afirst write operation WRITE1 of storing the first write data TRAN_WDATA1stored in the first write buffer in the nonvolatile memory devices C40,C50 and C60 is started and a time at which the performance of a secondwrite operation WRITE2 of storing the second write data TRAN_WDATA2stored in the second write buffer in the nonvolatile memory devices C40,C50 and C60 is started are not synchronized. Hence, there is a highpossibility that a time at which the performance of the first writeoperation is completed and a time at which the performance of the secondwrite operation is completed have a large difference.

Therefore, as in the case of a first synchronization operation shown inFIG. 96, the controller C30 may not synchronize, when a performance timeof the first flush operation FLUSH1 and a performance time of the secondflush operation FLUSH2 are not synchronized, a time at which a firstacknowledgement signal ACK1 for notifying the host C10 that theperformance of the first write operation WRITE1 linked to the firstflush operation FLUSH1 is completed is transferred to the host C10 and atime at which a second acknowledgement signal ACK2 for notifying thehost C10 that the performance of the second write operation WRITE2linked to the second flush operation FLUSH2 is completed is transferredto the host C10.

Because it is assumed in FIG. 8D that a performance time of the firstflush operation FLUSH1 and a performance time of the second flushoperation FLUSH2 are not synchronized, it is impossible that the secondsynchronization operation shown in FIGS. 9C and 9D is performed.

Referring again to FIG. 8D, after completing the performance of thesecond write operation WRITE2, the controller C30 resets the setting forthe second write buffer for exclusive use for the second transaction.That is, the controller C30 has used the second write buffer C32 as thesecond write buffer for exclusive use for the second transaction, bysetting the second exclusive use option for the second write buffer C32among the four write buffers C31, C32, C33 and C34 allocated in thevolatile memory 144, at the third time. Therefore, by resetting thesecond exclusive use option for the second write buffer after completingthe performance of the second write operation WRITE2 at the third time,the second write buffer C32 having been used as the second write buffermay not be used for exclusive use for the second transaction, likebefore the third time. Namely, the second write buffer C32 having beenexclusively used to store the second write data TRAN_WDATA2 at the thirdtime may be used to store, for example, normal write data NMAL_WDATA,after the third time.

Conversely, since it is a state in which the first flush operationFLUSH1 and the following first write operation WRITE1 are not performedfor the first write buffer, the first exclusive use option iscontinuously maintained for the first write buffer even after the thirdtime, and the first write buffer is continuously used exclusively forthe first transaction.

Referring to FIG. 8E, it may be assumed that, at a third time successiveto the second time shown in FIG. 8B, total seven pieces of the writedata WDATA are inputted from the host C10. A sequence in which the sevenpieces of the write data WDATA are inputted from the host C10 is notdefined in advance, and it may be assumed that they are inputtedrandomly.

In detail, the controller C30 checks the transaction ID information TRIDof the respective seven pieces of the write data WDATA inputted from thehost C10 at the third time, and classifies the seven pieces of the writedata WDATA into one piece of the first write data TRAN_WDATA1, fourpieces of the second write data TRAN_WDATA2 and two pieces of the normalwrite data NMAL_WDATA.

In further detail, the controller C30 determines that, among the sevenpieces of the write data WDATA inputted from the host C10 at the thirdtime, 3 as one piece of the write data WDATA of which transaction IDinformation TRID has the value of 1 is write data WDATA which is groupedinto the first transaction, and classifies it into the first write dataTRAN_WDATA1.

At this time, it is a state in which, through the operation at thesecond time described above with reference to FIG. 8B, the third writebuffer C33 among the four write buffers C31, C32, C33 and C34 allocatedin the volatile memory 144 has already been set for exclusive use forthe first transaction and is being used as the first write buffer forstoring the first write data TRAN_WDATA1.

Therefore, the controller C30 immediately stores 3 grouped into thefirst write data TRAN_WDATA1 in the first write buffer at the third timewithout a separate additional operation. At this time, it is a state inwhich, through the operation at the second time described above withreference to FIG. 8B, the controller C30 has set the third write bufferC33 capable of storing a total of six pieces of the write data, as thefirst write buffer for exclusive use for the first transaction, hasstored only 0, 1 and 2 as three pieces of the write data, and has kept aspace available for three pieces of the write data.

Because of this fact, the controller C30 immediately stores 3 groupedinto the first write data TRAN_WDATA1 in the first write buffer at thethird time without a separate additional operation. In this way, as 3grouped into the first write data TRAN_WDATA1 is stored in the firstwrite buffer at the third time, it becomes a state in which the firstwrite data TRAN_WDATA1 are stored in a space for four pieces of thewrite data in a total empty space capable of storing six pieces of thewrite data which is included in the first write buffer.

In summary, after additionally storing 3 as the one piece of the firstwrite data TRAN_WDATA1 inputted from the host C10 at the third time, inthe third write buffer C33 which is set as the first write buffer forexclusive use for the first transaction at the second time describedabove, the controller C30 keeps a space available for two remainingpieces of the write data empty.

At a time when 0, 1, 2 and 3 as the first write data TRAN_WDATA1 groupedinto the first transaction are stored in the first write buffer, thecontroller C30 may receive an information that the first transaction isaborted, from the host C10. For example, after 3 grouped into the firstwrite data TRAN_WDATA1 is stored in the first write buffer, a separatecommand including the abort information of the first transaction may betransmitted from the host C10. According to this fact, it may be checkedthat, in a state in which only 0, 1, 2 and 3 as the first write dataTRAN_WDATA1 grouped into the first transaction are stored in the firstwrite buffer, the first transaction is aborted (Transaction Abort).

Further, the controller C30 determines that, among the seven pieces ofthe write data WDATA inputted from the host C10 at the third time, 110,111, 112 and 113 as four pieces of the write data WDATA of whichtransaction ID information TRID have the value of 2 are write data WDATAwhich are grouped into the second transaction, and classifies them intothe second write data TRAN_WDATA2.

In a second write command (not shown) corresponding to 110 as start dataamong 110, 111, 112 and 113 grouped into the second write dataTRAN_WDATA2, the second total size information TTSIZE2 is included.Thus, the controller C30 may check from the second write commandcorresponding to 110 that the second total size information TTSIZE2 is4.

In this way, after checking that the second total size informationTTSIZE2 is 4, the controller C30 checks whether there is a write bufferhaving an empty space capable of storing total four pieces of the secondwrite data TRAN_WDATA2 which are grouped into the second transaction,among the remaining write buffers C31, C32 and C34 except the firstwrite buffer set for exclusive use for the first transaction among thefour write buffers C31, C32, C33 and C34 allocated in the volatilememory 144.

As a result of the checking, it is a state in which the third writebuffer C33 among the four write buffers C31, C32, C33 and C34 has beenset as the first write buffer for exclusive use for the firsttransaction at the second time described above.

Therefore, whether there is a write buffer having an empty space capableof storing a total of four pieces of the second write data TRAN_WDATA2which are grouped into the second transaction, among the remaining threewrite buffers C31, C32 and C34 except the third write buffer C33, ischecked.

As a result of the checking, because a total of four pieces of thenormal write data NMAL_WDATA have been stored in the first write bufferC31 among the three write buffers C31, C32 and C34 as two pieces of thenormal write data NMAL_WDATA are stored at each of the first time andthe second time described above, it is a state in which the first writebuffer CM has an empty space available for two other pieces of the writedata. Therefore, the first write buffer C31 is not suitable foraccommodating a total of four pieces of the second write dataTRAN_WDATA2 which are grouped into the second transaction.

Because the two pieces of the normal write data NMAL_WDATA have beenstored in the second write buffer C32 among the three write buffers C31,C32 and C34 at the first time described above, it is a state in whichthe second write buffer C32 has an empty space available for four piecesof the write data. Therefore, the second write buffer C32 is suitablefor accommodating a total of four pieces of the second write dataTRAN_WDATA2 which are grouped into the second transaction.

Because no write data has been stored in the fourth write buffer C34among the three write buffers C31, C32 and C34 at the first time and thesecond time described above, it is a state in which the fourth writebuffer C34 has an empty space capable of storing six pieces of the writedata. Therefore, the fourth write buffer C34 is suitable foraccommodating a total of four pieces of the second write dataTRAN_WDATA2 which are grouped into the second transaction.

In other words, an empty space capable of accommodating the seconddetermined size exists in each of one or more write buffers C32 and C34among the three write buffers C31, C32 and C34.

In this way, because each of one or more write buffers C32 and C34 hasan empty space capable of accommodating the second determined size, thecontroller C30 sets the second exclusive use option for a write bufferof which size of an empty space is relatively smaller, and manages thecorresponding write buffer as the second write buffer. That is, thecontroller C30 sets the second exclusive use option for the second writebuffer C32 of which size of an empty space is relatively smaller betweenthe second write buffer C32 and the fourth write buffer C34 each havingan empty space equal to or larger than the second determined size, andmanages the second write buffer C32 as the second write buffer.

In this way, the controller C30 may check the second total sizeinformation TTSIZE2 before 110 as the start data among 110, 111, 112 and113 grouped into the second write data TRAN_WDATA2 is inputted, andthereby, may set the second write buffer C32 among the four writebuffers C31, C32, C32 and C34 allocated in advance in the volatilememory 144, as the second write buffer for exclusive use for the secondtransaction.

Thus, each time each of the four pieces of the second write dataTRAN_WDATA2 grouped into the second transaction among the seven piecesof the write data WDATA inputted from the host C10 is inputted at thethird time, the controller C30 stores each of the four pieces of thesecond write data TRAN_WDATA2 in the second write buffer which is setfor exclusive use for the second transaction.

In this way, as 110, 111, 112 and 113 grouped into the second write dataTRAN_WDATA2 are stored in the second write buffer at the third time, itbecomes a state in which the second write data TRAN_WDATA2 are stored inthe entire empty space capable of storing four pieces of the write datawhich is included in the second write buffer.

At a time when 110, 111, 112 and 113 as the second write dataTRAN_WDATA2 grouped into the second transaction are stored in the secondwrite buffer and thus the second write data TRAN_WDATA2 are stored inthe entire empty space capable of storing four pieces of the write datawhich is included in the second write buffer, the controller C30 maycheck that it is a state in which the commit of the second transactionis completed (Transaction Complete).

In summary, by selecting the second write buffer C32 having the spacecapable of storing a total of four pieces of the write data as thesecond write buffer for exclusive use for the second transaction at thethird time and storing 110, 111, 112 and 113 as the four pieces of thesecond write data TRAN_WDATA2 inputted from the host C10, the controllerC30 may check that it is a state in which the commit of the secondtransaction is completed (Transaction Complete).

Moreover, the controller C30 determines that, among the seven pieces ofthe write data WDATA inputted from the host C10 at the third time, G andH as write data WDATA of which transaction ID information TRID are notset to any value are write data WDATA which are not grouped into atransaction, and classifies them into the normal write data NMAL_WDATA.

In succession, the controller C30 checks whether there is a write bufferwhich is set for exclusive use for a transaction, among the four writebuffers C31, C32, C33 and C34 allocated in the volatile memory 144, atthe third time. As a result of the checking, it is a state in which thethird write buffer C33 is set for exclusive use for the firsttransaction and the second write buffer C32 is set for exclusive use forthe second transaction at the third time. For reference, in order forthe second write buffer C32 to be set as the second write buffer forexclusive use for the second transaction at the third time, at least onepiece of the second write data TRAN_WDATA2 should be inputted.Therefore, it is assumed that FIG. 3D represents a case where at leastone piece of the second write data TRAN_WDATA2 is inputted earlier thanthe normal write data NMAL_WDATA.

Thus, the controller C30 may store G and H as the two pieces of thenormal write data NMAL_WDATA inputted from the host C10 at the thirdtime, by appropriately distributing them over the remaining writebuffers C31 and C34 except the third write buffer C33 set for exclusiveuse for the first transaction and the second write buffer C32 set forexclusive use for the second transaction among the four write buffersC31, C32, C33 and C34. For example, in the figure, G and H as the twopieces of the normal write data NMAL_WDATA inputted from the host C10 atthe third time are stored in the fourth write buffer C34.

In summary, the controller C30 stores G and H as the two pieces of thenormal write data NMAL_WDATA inputted from the host C10 at the thirdtime, in the fourth write buffer C34 among the four write buffers C31,C32, C33 and C34. As a result, in the fourth write buffer C34 having thestorage space capable of storing six pieces of the write data, the twopieces of the normal write data NMAL_WDATA are stored at the third time,and a space remains available for four pieces of the write data.

in the state as shown in FIG. 8E, since the first transaction is abortedand the second transaction is commit-completed, it is a case in which itis not necessary to perform a flush operation for the first write bufferand the second write buffer should be flushed.

When the state shown in FIG. 8B is changed to the state shown in FIG.8D, the first transaction is converted into a state in which it isaborted, and the second transaction is converted into a state in whichthe commit thereof is completed. Therefore, in the state as in FIG. 8E,it is impossible that the commit of the first transaction is completed.Thus, it may be determined that the first transaction is not committedwithin the set first time interval from a time at which the commit ofthe second transaction is completed.

In this way, in the case where the first transaction is abortedseparately from that the commit of the second transaction is completed,the controller C30 discards the first write data TRAN_WDATA1 stored inthe first write buffer, in correspondence to the abort of the firsttransaction, and then, resets the setting for the first write buffer forexclusive use for the first transaction. That is, the controller C30 hasused the third write buffer C33 as the first write buffer for exclusiveuse for the first transaction, by setting the first exclusive use optionfor the third write buffer C33 among the four write buffers C31, C32,C33 and C34 allocated in the volatile memory 144, at the second time.Therefore, after discarding the first write data TRAN_WDATA1 stored inthe first write buffer, in correspondence to the abort of the firsttransaction at the third time, as the setting for the first write bufferfor exclusive use for the first transaction is reset, the third writebuffer C33 having been used as the first write buffer may not be usedfor exclusive use for the first transaction, like before the secondtime. Namely, the third write buffer C33 having been exclusively used tostore the first write data TRAN_WDATA1 at the second time and the thirdtime may be used to store, for example, normal write data NMAL_WDATA,after the third time.

Further, the second flush operation FLUSH2 is performed for the secondwrite buffer in correspondence to that the commit of the secondtransaction is completed, separately from that the first transaction isaborted, and accordingly, the second write operation WRITE2 of storingthe second write data TRAN_WDATA2 stored in the second write buffer inthe nonvolatile memory devices C40, C50 and C60 is performed.

Since it is assumed in FIG. 8E that a first flush operation FLUSH1 forthe first write buffer is not performed, the first synchronizationoperation and the second synchronization operation shown in FIGS. 9A to9D are not performed.

Referring again to FIG. 8E, after completing the performance of thesecond write operation WRITE2, the controller C30 resets the setting forthe second write buffer for exclusive use for the second transaction.That is, the controller C30 has used the second write buffer C32 as thesecond write buffer for exclusive use for the second transaction, bysetting the second exclusive use option for the second write buffer C32among the four write buffers C31, C32, C33 and C34 allocated in thevolatile memory 144, at the third time. Therefore, by resetting thesecond exclusive use option for the second write buffer after completingthe performance of the second write operation WRITE2 at the third time,the second write buffer C32 having been used as the second write buffermay not be used for exclusive use for the second transaction, likebefore the third time. Namely, the second write buffer C32 having beenexclusively used to store the second write data TRAN_WDATA2 at the thirdtime may be used to store, for example, normal write data NMAL_WDATA,after the third time.

As is apparent from the above descriptions, the memory system C20 inaccordance with the second embodiment of the present disclosure may setthe first exclusive use option for the first write buffer among theplurality of write buffers C31, C32, C33 and C34 allocated in thevolatile memory 144, when the first write data TRAN_WDATA1 which aregrouped into the first transaction are inputted from the host C10, andmay exclusively use the first write buffer for the first transaction.Also, the memory system C20 in accordance with the second embodiment ofthe present disclosure may set the second exclusive use option for thesecond write buffer among the remaining write buffers except the firstwrite buffer among the plurality of write buffers C31, C32, C33 and C34allocated in the volatile memory 144, when the second write dataTRAN_WDATA2 which are grouped into the second transaction are inputtedfrom the host C10, and may exclusively use the second write buffer forthe second transaction. The first write buffer and the second writebuffer may be distinguished from each other. Through this, the memorysystem C20 in accordance with the second embodiment of the presentdisclosure may effectively manage transaction write data.

Further, the memory system C20 in accordance with the second embodimentof the present disclosure synchronizes a time at which a first flushoperation to be performed in the first write buffer is performed whenthe first transaction is committed and a time at which a second flushoperation to be performed in the second write buffer is performed whenthe second transaction is committed, to the maximum within a possiblerange. Through this, the first write operation WRITE1 of storing thefirst write data TRAN_WDATA1 stored in the first write buffer in thenonvolatile memory devices C40, C50 and C60 and the second writeoperation WRITE2 of storing the second write data TRAN_WDATA2 stored inthe second write buffer in the nonvolatile memory devices C40, C50 andC60 may be started by being synchronized, and a possibility tointensively store the first write data TRAN_WDATA1 and the second writedata TRAN_WDATA2 may be increased by collectively storing them in aspecific storage space of the nonvolatile memory devices C40, C50 andC60. Namely, an algorithm for ensuring the first transaction and thesecond transaction may be simplified.

Moreover, the memory system C20 in accordance with the second embodimentof the present disclosure maximally synchronizes within a possible rangetimes at which the first and second acknowledgement signals ACK1 andACK2 are transmitted to the host C10 to notify the host C10 that thesynchronized first and second write operations WRITE1 and WRITE2 arecompleted when the first and second write buffers C32 and C33 areflushed in a synchronized state. That is, the memory system C20 maytransfer the two acknowledgement signals ACK1 and ACK2 to the host C10at one timing. Through this, the number of times by which anacknowledgement signal is transmitted to the host C10 from the memorysystem C20 may be minimized.

FIGS. 10A to 10C are flow charts to assist in the explanation of theoperation of the memory system in accordance with the second embodimentof the present disclosure.

Referring to FIG. 10A, the operation of the memory system C20 inaccordance with the second embodiment of the present disclosure isstarted when write data WDATA is transmitted from the host C10 to thememory system C20 (L5).

Whether the write data WDATA transmitted at the step L5 is start data ofa transaction is checked (L10).

In the case where the write data WDATA is start data of a transaction atthe step L10 (YES), the memory system C20 searches at least one writebuffer suitable for storing transaction data among the plurality ofwrite buffers C31, C32, C33 and C34 allocated in advance in the volatilememory 144 disposed therein (Search Suitable WRITE Buffer), and sets theat least one write buffer as a private write buffer for exclusive usefor a transaction (Set Private WRITE Buffer) (L20). The searching of atleast one write buffer suitable for storing transaction data at the stepL20 means that at least one write buffer including an empty space equalto or larger than the total size of a transaction identified accordingto a total size information TTSIZE transferred together with the startdata of the transaction at the step L10 is searched.

At the step L20, new write buffers are set as private write buffers forexclusive use for transactions, by the number corresponding to the kindsof transactions (Set Private WRITE Buffer). That is, a first privatewrite buffer for exclusive use for a first transaction is set for thefirst transaction, and a second private write buffer for exclusive usefor a second transaction is set for the second transaction.

In the case where the write data WDATA is not start data of atransaction at the step L10 (NO), it may be regarded that the write dataWDATA transmitted at the step L5 is normal write data NMAL_WDATA oranother data other than start data of the transaction.

In the case where the write data WDATA transmitted at the step L5 isnormal write data NMAL_WDATA, the write data WDATA is stored in a publicwrite buffer (Public WRITE buffer) which is not set for exclusive usefor a transaction (L30).

In the case where the write data WDATA transmitted at the step L5 isanother data other than start data of the transaction, the write dataWDATA is stored in the private write buffer (Private WRITE Buffer) whichis set for exclusive use for the transaction at the step L20 (L30). Atthe step L30, it is checked which kind of a transaction the write dataWDATA transmitted at the step L5 is, and the write data WDATA is storedin a private write buffer for exclusive use for a transaction incorrespondence to the checked transaction. In other words, at the stepL30, in the case where the write data WDATA transmitted at the step L5is another data of the first transaction, the write data WDATA is storedin the first private write buffer for exclusive use for the firsttransaction, and, in the case where the write data WDATA transmitted atthe step L5 is another data of the second transaction, the write dataWDATA is stored in the second private write buffer for exclusive use forthe second transaction.

After the step L30, whether a buffer of which commit is completed existsamong private write buffers for exclusive use for transactions ischecked (L40).

In the case where a buffer of which commit is completed does not existat the step L40 (NO), a separate operation is not performed until newwrite data WDATA is inputted at the step L5.

In the case where a buffer of which commit is completed exists at thestep L40 (YES), whether the commit of another transaction is completedis checked (L50). In other words, through the step L40 and the step L50,whether at least two transactions are committed may be checked.

In the case where only one private write buffer is committed as a resultof the step L50 (NO), only the one private write buffer which iscommitted is flushed alone (L80). The private write buffer which isflushed at the step L80 is not flushed simultaneously with anotherprivate write buffer.

In the case where at least two private write buffers are committed as aresult of the step L50 (YES), whether the commit times of the at leasttwo private write buffers are within a set first time interval (SETTIME1) is checked (L60). That is, whether the commit time of a privatewrite buffer (Private WRITE Buffer<L40>) of which commit is checked atthe step L40 and the commit time of a private write buffer (PrivateWRITE Buffer<L50>) of which commit is checked at the step L50 are withinthe set first time interval (SET TIME1) is checked (L60).

In the case where the commit times of the at least two private writebuffers exceed the set first time interval (SET TIME1) at the step L60(NO), flush operations for the at least two private write buffers whichare commit-completed are not synchronized (L80). That is, a flushoperation for the private write buffer (Private WRITE Buffer<L40>) ofwhich commit is checked at the step L40 and a flush operation for theprivate write buffer (Private WRITE Buffer<L50>) of which commit ischecked at the step L50 are not synchronized (L80).

In the case where difference between the commit times of the at leasttwo private write buffers are within the set first time interval (SETTIME1) at the step L60 (YES), flush operations for the at least twoprivate write buffers which are commit-completed are synchronized (L70).That is, a flush operation for the private write buffer (Private WRITEBuffer<L40>) of which commit is checked at the step L40 and a flushoperation for the private write buffer (Private WRITE Buffer<L50>) ofwhich commit is checked at the step L50 are synchronized (L70).

After the flush operations for the at least two private write bufferswhich are commit-completed are synchronized at the step L70, any oneoperation of two operations may he selected and performed by referringto FIGS. 10B and 10C as will be described below.

Referring to FIG. 10B, in correspondence to that the flush operationsfor the at least two private write buffers which are commit-completedare synchronized at the step L70, at least two write operations (Writeto Non-Volatile Memory, Private WRITE Buffer <L40 & L50>) of storing thetransaction data stored in the at least two private write buffers, inthe nonvolatile memory devices C40, C50 and C60, are synchronized (L90).

Since the flush operations for the at least two private write bufferswhich are commit-completed are synchronized and accordingly the at leasttwo write operations are synchronized at the step L70 and the step L90,in FIG. 10B, a separate condition is not additionally checked, and timesat which at least two acknowledgement signals (ACK<L40 & L50> of WriteComplete corresponding to (Private WRITE) Buffer<L40 & L50>) fornotifying the host C10 that the at least two write operations arecompleted are transmitted to the host C10 are synchronized (L100).

Referring to FIG. 10C, in correspondence to that the flush operationsfor the at least two private write buffers which are commit-completedare synchronized at the step L70, at least two write operations (Writeto Non-Volatile Memory, Private WRITE Buffer <L40 & L50>) of storing thetransaction data stored in the at least two private write buffers, inthe nonvolatile memory devices C40, C50 and C60, are synchronized (L90).

After the flush operations for the at least two private write bufferswhich are commit-completed are synchronized and accordingly the at leasttwo write operations are synchronized at the step L70 and the step L90,in FIG. 10C, whether the times at which the at least two writeoperations are completed are within a set second time interval (SETTIME2) is checked (L110).

In the case where the times at which the at least two write operationsare completed are within the set second time interval (SET TIME2) at thestep L110 (YES), times at which at least two acknowledgement signals(ACK<L40 & L50> of Write Complete corresponding to (Private WRITE)Buffer<L40 & L50>) for notifying the host C10 that the at least twowrite operations are completed are transmitted to the host C10 aresynchronized (L120).

In the case where the times at which the at least two write operationsare completed exceed the set second time interval (SET TIME2) at thestep L110 (NO), times at which at least two acknowledgement signals(ACK<L40 & L50> of Write Complete corresponding to (Private WRITE)Buffer<L40 & L50>) for notifying the host C10 that the at least twowrite operations are completed are transmitted to the host C10 are notsynchronized (L130).

Although various embodiments have been illustrated and described, itwill be apparent to those skilled in the art in light of the presentdisclosure that various changes and modifications may be made withoutdeparting from the spirit and scope of the invention as defined in thefollowing claims.

What is claimed is:
 1. A memory system comprising: a nonvolatile memorydevice; a volatile memory suitable for temporarily storing write datainputted from a host; and a controller suitable for: allocating a normalwrite buffer in the volatile memory when normal write data, which arenot grouped into a transaction, are inputted from the host, allocating afirst write buffer in the volatile memory when first write data, whichare grouped into a first transaction and first total size information ona total size of the first transaction, are inputted, allocating a secondwrite buffer in the volatile memory when second write data, which aregrouped into a second transaction and second total size information on atotal size of the second transaction, are inputted, managing sizes ofthe first and second write buffers to change them in response to thefirst and second total size information, respectively, and managing asize of the normal write buffer to fix it to a set size.
 2. The memorysystem according to claim 1, wherein the controller further: checks afirst determined size for the first e data according to the first totalsize information, and allocates the first write buffer by an amount ofthe first determined size in the volatile memory, and checks a seconddetermined size for the second write data according to the second totalsize information, and allocates the second write buffer by an amount ofthe second determined size in the volatile memory.
 3. The memory systemaccording to claim 2, wherein the controller further: checks whether thefirst transaction is committed or aborted, for the first write datastored in the first write buffer; performs a first write operation ofstoring the first write data stored in the first write buffer in thenonvolatile memory device by performing a first flush operation for thefirst write buffer, in the case where the first transaction is checkedas being committed, and then releases the first write buffer in thevolatile memory, and releases the first write buffer in the volatilememory in the case where the first transaction is checked as beingaborted.
 4. The memory system according to claim 3, wherein thecontroller further: checks whether the second transaction is committedor aborted, for the second write data stored in the second write buffer,performs a second write operation of storing the second write datastored in the second write buffer in the nonvolatile memory device byperforming a second flush operation for the second write buffer, in thecase where the second transaction is checked as being committed, andthen releases the second write buffer in the volatile memory, andreleases the second write buffer in the volatile memory in the casewhere the second transaction is checked as being aborted.
 5. The memorysystem according to claim 4, wherein the controller further:synchronizes a start time of the first flush operation and a start timeof the second flush operation in the case where a time at which commitof the first transaction is checked and a time at which commit of thesecond transaction is checked are within a set first time interval. 6.The memory system according to claim 5, wherein, when the start time ofthe first flush operation and the start time of the second flushoperation are synchronized, the controller synchronizes a time at whicha first acknowledgement signal corresponding to completion of the firstwrite operation is transferred to the host and a time at which a secondacknowledgement signal corresponding to completion of the second writeoperation is transferred to the host.
 7. The memory system according toclaim 5, wherein, when a time at which a first acknowledgement signal isgenerated and a time at which a second acknowledgement signal isgenerated are within a set second time interval, the controllersynchronizes a time at which the first acknowledgement signal istransferred to the host and a time at which the second acknowledgementsignal is transferred to the host.
 8. The memory system according toclaim 4, wherein: the controller receives a plurality of write commandsrespectively corresponding to the write data, from the host, transactioninformation of the respective write data corresponding to the writecommands are respectively included in the write commands, transactioninformation of each of the write data includes transaction ID(identification) information, commit information and abort information,the first total size information is additionally included in a writecommand corresponding to start data of the first transaction among thefirst write data, and the second total size information is additionallyincluded in a write command corresponding to start data of the secondtransaction among the second write data.
 9. The memory system accordingto claim 8, wherein the controller further: checks transaction IDinformation in the transaction information of the respective write data,stores the first write data by allocating the first write buffer in thevolatile memory in the case where the transaction ID information of thefirst write data which are grouped into the first transaction arechecked as being set to a first value, stores the second write data byallocating the second write buffer in the volatile memory in the casewhere the transaction ID information of the second write data which aregrouped into the second transaction are checked as being set to a secondvalue, and stores the normal write data by allocating the normal writebuffer in the volatile memory in the case where the transaction IDinformation of the normal write data are checked as not being set andthus which are not grouped into a transaction.
 10. A memory systemcomprising: a nonvolatile memory device; a volatile memory suitable fortemporarily storing write data inputted from a host; and a controllersuitable for: allocating a plurality of write buffers, each of which hasa defined size, in the volatile memory, storing normal write data, whichare inputted from the host and are not grouped into a transaction, inwrite buffers which are not set for exclusive use for transactions, andsetting, when first write data which are grouped into a firsttransaction and first total size information on a total size of thefirst transaction are inputted from the host, a first exclusive useoption for exclusively using at least one first write buffer among thewrite buffers, for the first transaction, according to the first totalsize information.
 11. The memory system according to claim 10, whereinthe controller further: checks respective empty spaces of the writebuffers at a time when the first write data are inputted from the host,sets the first exclusive use option for a minimum number of writebuffers among the write buffers, according to the checked empty spacesand the first total size information, and uses the minimum number ofwrite buffers as the at least one first write buffer.
 12. The memorysystem according to claim 11, wherein the controller further: sets, whensecond write data which are grouped into a second transaction and secondtotal size information on a total size of the second transaction areinputted from the host, a second exclusive use option for exclusivelyusing at least one second write buffer among remaining write buffersexcluding the first write buffer, for the second transaction, accordingto the second total size information.
 13. The memory system according toclaim 12, wherein the controller further: checks respective empty spacesof the remaining write buffers at a time when the second write data areinputted from the host, sets the second exclusive use option for aminimum number of write buffers among the remaining write buffers,according to the checked empty spaces and the second total sizeinformation, and uses the minimum number of write buffers as the atleast one second write buffer.
 14. The memory system according to claim13, wherein the controller further: checks whether the first transactionis committed or aborted, for the first write data stored in the at leastone first write buffer, performs a first write operation of storing thefirst write data stored in the at least one first write buffer in thenonvolatile memory device by performing a first flush operation for theat least one first write buffer, in the case where the first transactionis checked as being committed, and then resets the first exclusive useoption for the at least one first write buffer, and discards the firstwrite data stored in the at least one first write buffer in the casewhere the first transaction is checked as being aborted, and then resetsthe first exclusive use option for the at least one first write buffer.15. The memory system according to claim 14, wherein the controllerfurther: checks whether the second transaction is committed or aborted,for the second write data stored in the at least one second writebuffer, performs a second write operation of storing the second writedata stored in the at least one second write buffer in the nonvolatilememory device by performing a second flush operation for the at leastone second write buffer, in the case where the second transaction ischecked as being committed, and then resets the second exclusive useoption for the at least one second write buffer, and discards the secondwrite data stored in the at least one second write buffer in the casewhere the second transaction is checked as being aborted, and thenresets the second exclusive use option for the at least one second writebuffer.
 16. The memory system according to claim 15, wherein thecontroller further: synchronizes a start time of the first flushoperation and a start time of the second flush operation in the casewhere a time at which commit of the first transaction is checked and atime at which commit of the second transaction is checked are within aset first time interval.
 17. The memory system according to claim 16,wherein, when the start time of the first flush operation and the starttime of the second flush operation are synchronized, the controllersynchronizes a time at which a first acknowledgement signalcorresponding to completion of the first write operation is transferredto the host and a time at which a second acknowledgement signalcorresponding to completion of the second write operation is transferredto the host.
 18. The memory system according to claim 16, wherein, whena time at which a first acknowledgement signal corresponding tocompletion of the first write operation is generated and a time at whicha second acknowledgement signal corresponding to completion of thesecond write operation is generated are within a set second timeinterval, the controller synchronizes a time at which the firstacknowledgement signal is transferred to the host and a time at whichthe second acknowledgement signal is transferred to the host.
 19. Thememory system according to claim 14, wherein: the controller receivesfrom the host a plurality of write commands respectively correspondingto the write data, transaction information of the respective write datacorresponding to the write commands are respectively included in thewrite commands, transaction information of each of the write dataincludes transaction ID (identification) information, commit informationand abort information, the first total size information is additionallyincluded in a write command corresponding to start data of the firsttransaction among the first write data, and the second total sizeinformation is additionally included in a write command corresponding tostart data of the second transaction among the second write data. 20.The memory system according to claim 19, wherein the controller further:checks transaction ID information in the transaction information of therespective write data, stores the first write data by setting the firstwrite buffer among the write buffers in the case where the transactionID information of the first write data which are grouped into the firsttransaction are checked as being set to a first value, stores the secondwrite data by setting the at least one second write buffer among theremaining write buffers in the case where the transaction ID informationof the second write data which are grouped into the second transactionare checked as being set to a second value, and stores the normal writedata in remaining write buffers except the first and second writebuffers among the write buffers, in the case where the transaction IDinformation of the normal write data are checked as not being set andthus which are not grouped into a transaction.